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
Is your feature request related to a problem? Please describe.
The builtin metrics provided by this library are out-of-date with respect to the OTel specifications and with respect to the Go-teams runtime/metrics package. A complete update to this problem includes:
New instrumentation package to expose process cpu timing, including proposed candidates for new Go runtime/metrics: CPU runtime and timing metrics #269.
Describe the solution you'd like
See the links above for individual changes.
To combine these into a new otel-launcher-go release, one additional option will be needed. I suggest the following:
LS_METRICS_BUILTINS_NAMED=one,two,three
where one, two, and three are short-names of known builtin instrumentation. We will not change any defaults in the 1.x otel-launcher-go release series, instead we will provide configuration options to choose the new experimental instrumentation, for now. When otel-launcher-go 2.x is released, it can update to the new, preferred libraries by default. By then, we should be able to merge our new instrumentation with the upstream repository, probably in the form of new packages.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The builtin metrics provided by this library are out-of-date with respect to the OTel specifications and with respect to the Go-teams
runtime/metrics
package. A complete update to this problem includes:instrumentation/runtime
package to expose go-team's standardruntime/metrics
: New runtime/metrics instrumentation #267instrumentation/host
to stop it from exposing process cpu timing: Lightstep fork of go-contrib instrumentation/host metrics #268runtime/metrics
: CPU runtime and timing metrics #269.Describe the solution you'd like
See the links above for individual changes.
To combine these into a new otel-launcher-go release, one additional option will be needed. I suggest the following:
LS_METRICS_BUILTINS_NAMED=one,two,three
where one, two, and three are short-names of known builtin instrumentation. We will not change any defaults in the 1.x otel-launcher-go release series, instead we will provide configuration options to choose the new experimental instrumentation, for now. When otel-launcher-go 2.x is released, it can update to the new, preferred libraries by default. By then, we should be able to merge our new instrumentation with the upstream repository, probably in the form of new packages.
The text was updated successfully, but these errors were encountered: