James Moessis

benchmarking PR: https://github.com/open-telemetry/opentelemetry-java/pull/3986

@jsuereth Yeah, the `MapCounter` has unnecessary safeguards for thread safety. Since it's purely behind `Handle` some fo those can be taken away. Anyway, I doubt the most efficient solution uses...

True, worst case the memory difference is quite high. It's even doubly worse than that since there's `320*postivebuckets` and `320*negativebuckets`. I imagine most user won't be using the maximum 320...

I noticed this problem too, is this going to get merged?

> Option 2: the metric receivers implementation should follow the specification and add namespaces. I like this option. Is there any reason that the metric receivers can't follow the datbabase...

Hello folks, I've just done a bunch of work on https://github.com/open-telemetry/build-tools/pull/79 and I believe it's close to being ready for merge. Please feel free to leave a review with any...

@trask pointed out in the Java SIG that resolution to https://github.com/open-telemetry/opentelemetry-specification/issues/2056 (http.target vs path & query) is a minor thing that would be nice. This is also something that most...

I think this is a good idea. I am not convinced that the semantic convention is the place where an attribute should be defined as sensitive or not. It could...

> Can you give a concrete example of an attribute that has different sensitivity depending on application? The `peer.ip` attribute that you mentioned is an example where the sensitivity depends...

Sorry, I meant user as in application owner.