Alex Boten

@MadVikingGod @carrbs an alternative is to generate the yaml struct tags and avoid the mapstructure middle step, see https://github.com/open-telemetry/opentelemetry-go-contrib/pull/5433 as an example

@pellared already started on this, please assign it to me when you have a moment

Traces and metrics both rely on the go sdk to export internal telemetry. This issue will be blocked by https://github.com/open-telemetry/opentelemetry-go/issues/3827 unless an alternative proposal is put forward until logs are...

Related to https://github.com/open-telemetry/opentelemetry-collector/issues/3460

@paprickar i do not. Maybe one of the @open-telemetry/python-maintainers can chime in with more info

One thing to note with this change is that metrics that are generated by an instrumentation library or by a component that instantiates its own metric will not be prefixed...

> @codeboten I updated #9767. It'd be great to merge that PR first in order to disable the grps/http instrumentation metrics by default before changing their names @dmitryax i think...

> ### Remaining work > > * [ ] Decide on [[docs/rfc] RFC about environment variables #9854 (comment)](https://github.com/open-telemetry/opentelemetry-collector/pull/9854#discussion_r1561181980) by raising this on the spec and seeing if we can align...

Let's merge this and change it as needed, the spec change was merged 👍🏻

I support!