-
Notifications
You must be signed in to change notification settings - Fork 566
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
Runtime instrumentation: Make runtime.uptime an Asynchronous Gauge #1341
Comments
In the prometheus exporter in open-telemetry/opentelemetry-collector-contrib this metric fails to get exported due to this error:
|
Can we have someone looking into this please? The incorrect type caused high error rate while exporting the metrics to Google Cloud. It reports |
Hello @MrAlias, i am currently working on a pull request for this issue. Can it be assigned to me? |
This is no longer relevant after #5780. The semantic conventions for this instrumentation no longer contain this metric: open-telemetry/semantic-conventions#981. |
Currently the
runtime.uptime
metric is reported as an Asynchronous Counter. Uptime as a concept is certainly monotonic which makes it seem like it should be a Counter, but it's also non-additive, it doesn't make sense to sum the uptime of different processes.Additionally reporting uptime as a Counter presents a problem when trying to use delta temporality. The obvious question you want to answer with a metric like this is "How long has my process been running?". Using delta temporality with uptime would force you to track the running sum of all data points since the process started.
Because runtime.uptime is not additive and we don't actually care about rates or sum I think it is best served as an Asynchronous Gauge.
The text was updated successfully, but these errors were encountered: