-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semantic conventions for go runtime metrics #535
Labels
enhancement
New feature or request
Comments
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 |
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: