Ken Finnigan
Ken Finnigan
Could maintainers from one group evaluate a separate group, rather than self evaluation?
> @kenfinnigan I like this idea conceptually, but anticipate practical problems where maintainers from SIG A won't have enough context about the day-to-day in SIG B. Agree it could be...
I'd agree with @anuraaga. The problem should be solved with documentation in MicroProfile making it clear that only the Tracing APIs are supported from the OpenTelemetry API dependency.
From my use of the Jaeger gRPC exporter, the Resource information is on every span as an attribute. Should that not be the case?
Apologies @jkwatson, I confused myself because in the Jaeger UI it includes them, which makes sense. Agree it's not set on each span, just visualized that way
I can find some time to take a crack at it
Personally, anyone using Micrometer today is more likely to want to stick with the Micrometer API, and would be more interested in a OTeL Registry for Micrometer as an alternative...
I'm fine with that. In creating the structs to match the spec I had err'd towards an array of strings as the spec supported a single string or an array...
@weyert how would that be represented in a struct?
> The metadata has a different purpose than the notations, though. The metadata is for the vendor to leverage e.g. for search, tagging. To display in a metadata panel. The...