Cijo Thomas

Slack discussion on the same topic : https://cloud-native.slack.com/archives/C01N3BC2W7Q/p1647409842604329 Np update on this yet, and hence no ETA.

https://github.com/open-telemetry/opentelemetry-dotnet/issues/3023 duplicate?

@vishweshbankwar - FYI . Might be related to the issue you are investigating about Activity.Current's reliability..

The naming was discussed a while ago : https://github.com/open-telemetry/opentelemetry-dotnet/pull/623#issuecomment-619222535 Please take a look, and see if that makes sense, or do you think we should revisit the name?

https://github.com/open-telemetry/opentelemetry-specification/pull/2215 This is removed from spec itself, for initial stable release, to be added later.

It won't be part of 1.4.0. The spec still does not have it unfortunately.

Since HttpClient creates the activity, their name will appear as the name and version. OTel instrumentation library "enriches" it. Users can further enrich it.. Collector can enrich more...

Yea I agree this is an issue. If a user changes some of the tags themselves, then the "schema_url" could no longer be valid. So anyone modifying a span, should...

This sounds reasonable change. https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/resource/semantic_conventions/README.md#service

mm. Yes it feels some change to spec would be needed, given its a "MUST" in the spec.