process: change process.uptime instrument to gauge (#1585)
This commit is contained in:
parent
fa564c9f67
commit
50ad22e026
|
|
@ -0,0 +1,22 @@
|
||||||
|
# Use this changelog template to create an entry for release notes.
|
||||||
|
#
|
||||||
|
# If your change doesn't affect end users you should instead start
|
||||||
|
# your pull request title with [chore] or use the "Skip Changelog" label.
|
||||||
|
|
||||||
|
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
|
||||||
|
change_type: breaking
|
||||||
|
|
||||||
|
# The name of the area of concern in the attributes-registry, (e.g. http, cloud, db)
|
||||||
|
component: process
|
||||||
|
|
||||||
|
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
|
||||||
|
note: Change process.uptime instrument to a gauge.
|
||||||
|
|
||||||
|
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
|
||||||
|
# The values here must be integers.
|
||||||
|
issues: [1518]
|
||||||
|
|
||||||
|
# (Optional) One or more lines of additional information to render under the primary note.
|
||||||
|
# These lines will be padded with 2 spaces and then inserted directly into the document.
|
||||||
|
# Use pipe (|) for multiline entries.
|
||||||
|
subtext:
|
||||||
|
|
@ -341,9 +341,10 @@ This metric is [recommended][MetricRecommended].
|
||||||
|
|
||||||
| Name | Instrument Type | Unit (UCUM) | Description | Stability |
|
| Name | Instrument Type | Unit (UCUM) | Description | Stability |
|
||||||
| -------- | --------------- | ----------- | -------------- | --------- |
|
| -------- | --------------- | ----------- | -------------- | --------- |
|
||||||
| `process.uptime` | Counter | `s` | The time the process has been running. [1] |  |
|
| `process.uptime` | Gauge | `s` | The time the process has been running. [1] |  |
|
||||||
|
|
||||||
**[1]:** Instrumentations SHOULD use counter with type `double` and measure uptime with at least millisecond precision
|
**[1]:** Instrumentations SHOULD use a gauge with type `double` and measure uptime in seconds as a floating point number with the highest precision available.
|
||||||
|
The actual accuracy would depend on the instrumentation and operating system.
|
||||||
|
|
||||||
<!-- markdownlint-restore -->
|
<!-- markdownlint-restore -->
|
||||||
<!-- prettier-ignore-end -->
|
<!-- prettier-ignore-end -->
|
||||||
|
|
|
||||||
|
|
@ -108,6 +108,8 @@ groups:
|
||||||
metric_name: process.uptime
|
metric_name: process.uptime
|
||||||
stability: experimental
|
stability: experimental
|
||||||
brief: "The time the process has been running."
|
brief: "The time the process has been running."
|
||||||
instrument: counter
|
note: |
|
||||||
|
Instrumentations SHOULD use a gauge with type `double` and measure uptime in seconds as a floating point number with the highest precision available.
|
||||||
|
The actual accuracy would depend on the instrumentation and operating system.
|
||||||
|
instrument: gauge
|
||||||
unit: "s"
|
unit: "s"
|
||||||
note: "Instrumentations SHOULD use counter with type `double` and measure uptime with at least millisecond precision"
|
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue