open-telemetry
/
semantic-conventions
mirror of https://github.com/open-telemetry/semantic-conventions.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Reduce restrictions on which metrics may be named utilization (#280)

This commit is contained in:
Tyler Helmuth 2023-09-18 09:44:11 -06:00 committed by GitHub
parent e880bddb63
commit 875cfefe7d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/general/metrics.md
View File

@ -166,8 +166,10 @@ over all attribute values SHOULD be equal to the **limit**.
- **utilization** - an instrument that measures the *fraction* of **usage** - **utilization** - an instrument that measures the *fraction* of **usage**
out of its **limit** should be called `entity.utilization`. For example, out of its **limit** should be called `entity.utilization`. For example,
`system.memory.utilization` for the fraction of memory in use. Utilization `system.memory.utilization` for the fraction of memory in use. Utilization can
values are in the range `[0, 1]`. be with respect to a fixed limit or a soft limit. Utilization values are
represended as a ratio and are typically in the range `[0, 1]`, but may go above 1
in case of exceeding a soft limit.
- **time** - an instrument that measures passage of time should be called - **time** - an instrument that measures passage of time should be called
`entity.time`. For example, `system.cpu.time` with attribute `state = idle | user `entity.time`. For example, `system.cpu.time` with attribute `state = idle | user