You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go runtime metrics are currently named runtime.go.*, which conflicts with the runtime metrics guidance: Metrics specific to a certain runtime environment should be prefixed with the runtime's top-level namespace {environment}.*, e.g., jvm.*
Which metrics from the go runtime are stable? What are the stability guarantees?
in case the prior art helps, we are putting the breaking JVM metrics changes that we are implementing as part of JVM metric stability behind OTEL_SEMCONV_STABILITY_OPT_IN=jvm (and will make them the default in upcoming Java Instrumentation 2.0)
For runtime semantic conventions, we currently only have JVM metrics defined: https://github.com/open-telemetry/semantic-conventions/tree/main/docs/runtime#semantic-conventions-for-runtime-environment. The Go SIG (discussed on 11/16/23) would like to agree on conventions in this repository before expanding the set of metrics offered by the go runtime instrumentation package: https://pkg.go.dev/go.opentelemetry.io/contrib/instrumentation/runtime#pkg-overview to minimize the churn to users.
Additional context:
Starting Questions/potential issues:
runtime.go.*
, which conflicts with the runtime metrics guidance:Metrics specific to a certain runtime environment should be prefixed with the runtime's top-level namespace {environment}.*, e.g., jvm.*
@MrAlias @pellared
The text was updated successfully, but these errors were encountered: