Cijo Thomas

Same/similar issue was reported https://github.com/open-telemetry/opentelemetry-rust/issues/3068#issuecomment-3084275740 too.

@rajkumar-rangaraj https://github.com/open-telemetry/opentelemetry-dotnet/issues/5701 - Unsure if there is anything particular to be done for traces here. Most likely none.

For metrics, the change would be here: https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry/Metrics/MetricStreamIdentity.cs#L139 It currently ignores Meter Tags, but it should be added now. A unit test exist to validate current behavior, that should be...

@msierks-pcln Can you sign the CLA, so we can consider contributions? It's a one-time process and is mandatory. If contributing on behalf of your employer, please do consult them before...

@brunobrolesi Thanks! Can you check if this is only place where Atomics were used? It's okay to do it in a follow up, if you are okay with that. (Trying...

@bantonsson This might be something interesting for you too. The prior PR has some ideas/suggestions.

Consider exploring this too, if working on moving the limits to Sdk package: To properly implement Attribute Limits for Span (Activity), we'd likely need some support from runtime library itself...

## Design Considerations 1. **Opt-in behavior** - Feature should be disabled by default to maintain backward compatibility 2. **Span name inclusion** - Decide whether to include the span name as...

> [@cijothomas](https://github.com/cijothomas) i can work on this, please can you assign me. Thanks! Please work on it incrementally - I listed several considerations, but we can start with the most...

OTel Metrics specification is not specifically written for server-side. It's quite general purpose. I don't see why the spec should have this warning at all.