Trask Stalnaker
Trask Stalnaker
just a note, I did find something in our current conventions which is both a metric and a metric name: `hw.voltage`
> If this restriction was put in place, making the `process.disk.io.direction` name illegal since `process.disk.io` is the metric name and thus cannot be a namespace, the attribute would need to...
this has come up in https://github.com/open-telemetry/opentelemetry-java-instrumentation/pull/11901 which is proposing metrics: * `camel.context.exchange` * `camel.context.exchange.completed` * `camel.context.exchange.inflight` * `camel.context.exchange.failed` * `camel.context.exchange.failed.handled` * `camel.context.exchange.redelivered` * `camel.context.exchange.redelivered.external`
closing in favor of the less invasive #7157
This requires opening a Service Desk ticket
From CNCF > Renamed https://lists.cncf.io/g/cncf-opentelemetry-community/topics to [[email protected]](mailto:[email protected]) > > Copied all unique members from > > https://lists.cncf.io/g/cncf-opentelemetry-contributors/topics > > https://lists.cncf.io/g/cncf-opentelemetry-comms/topics > > to [[email protected]](mailto:[email protected]) > > and locked the mailing...
New service desk ticket: https://cncfservicedesk.atlassian.net/servicedesk/customer/portal/1/CNCFSD-2914
it's been locked, let me know if we need to temporarily unlock it to change the PyPi email address
Closing as there does not appear to be interest from the necessary folks in order to move this forward at this time.
Closing as the messaging SIG is not currently active to review it