Trask Stalnaker
Trask Stalnaker
> The metrics defined by semantic conventions clearly promote dot-separated names, both for the metric names and for the metric attribute names. I think we should follow this pattern as...
thanks @luigidemasi!
In the Java SDK [you can create multiple metric readers from the same metric exporter](https://github.com/open-telemetry/opentelemetry-java/blob/a745d60e8d78f051f3ceb4ccbf2c9a6016e57986/sdk/metrics/src/main/java/io/opentelemetry/sdk/metrics/export/PeriodicMetricReader.java#L55).
@lalitb let me know when you all are decided and I can create the new team
@open-telemetry/rust-publishers created I added `rust-publishers` in between `rust-maintainers` and `rust-approvers`, can you check this and confirm this is the setup you want?
> > I added rust-publishers in between rust-maintainers and rust-approvers > > Does it mean that `rust-publishers` is now child team of `rust-approvers`, and the `rust-maintainers` the child of `rust-approvers`...
@lalitb sorry, just double checking that it's ok to close this, thanks!
hi @david-luna, can `OTEL_EXPORTER_OTLP_HEADERS` be used to override the user-agent header in those implementations?
thanks, sounds like a good clarification (one way or the other) in the specification
@chenlujjj we have recently kicked off an RPC semantic convention stability SIG and it would be interesting to us if you wanted to pursue this PR (cc @lmolkova)