Cijo Thomas

DS is out of band, so DS 9.0 can be used in any .NET versions, not just .NET 9. (OTel enforces that, as OTel **always** depend on the latest stable...

Move it out of 1.10 due to lack of owner. If anyone can lend hands, please reply here and we can re-add for 1.10

Moving out of 1.10, as some fixes mighjt be in upstream W3C specs. and no owner for this to make it ready by 1.10

No work has been done on this yet. @vishweshbankwar might have explored this a bit? We also got feedback about adding this particularly for the Metrics being dropped when it...

@dpk83 I believe you also mentioned the need to know how many metrics etc are being dropped, due to dimensioncap/other reasons.

I think this is an important enough thing to be provided by the SDK itself for every user (i.e whoever is willing to pay for the cost of storing the...

It got pushed out from 1.5, unfortunately. We should be doing this in 1.6. (it could be a different implementation for the metrics, to let users know if they are...

+1 to this issue from investigating issues with BatchExportProcessor which emits a [log about dropped items, but it does so only at the shutdown](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry/BatchExportProcessor.cs#L220). This leaves us with no good...

> My team is dealing with sporadic metric drops and we suspect it's due to cardinality limits being reached. `OTEL_DOTNET_EXPERIMENTAL_METRICS_EMIT_OVERFLOW_ATTRIBUTE=true` is your best option right now to detect this. https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/docs/metrics#cardinality-limits...

> @cijothomas Thank you for sharing! I'm having trouble following what's the behavior with overflow attribute enabled. We're using Histogram (from System.Diagnostics.Metrics) for our metrics so if we execute `someHistogram.Record(value,...