Skip to content

Commit

Permalink
Clarify when "count" is used instead of pluralization (open-telemetry…
Browse files Browse the repository at this point in the history
  • Loading branch information
tigrannajaryan authored and beeme1mr committed Aug 31, 2022
1 parent 3e96900 commit 4bc38ce
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions specification/metrics/semantic_conventions/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@
* [Name Reuse Prohibition](#name-reuse-prohibition)
* [Units](#units)
* [Pluralization](#pluralization)
+ [Use `count` Instead of Pluralization](#use-count-instead-of-pluralization)
- [General Metric Semantic Conventions](#general-metric-semantic-conventions)
* [Instrument Naming](#instrument-naming)
* [Instrument Units](#instrument-units)
Expand Down Expand Up @@ -105,6 +106,17 @@ should not be pluralized, even if many data points are recorded.
* `system.paging.faults`, `system.disk.operations`, and `system.network.packets`
should be pluralized, even if only a single data point is recorded.

#### Use `count` Instead of Pluralization

If the value being recorded represents the count of concepts signified
by the namespace then the metric should be named `count` (within its namespace).
The pluralization rule does not apply in this case.

For example if we have a namespace `system.processes` which contains all metrics related
to the processes then to represent the count of the processes we can have a metric named
`system.processes.count`. The suffix `count` here indicates that it is the count of
`system.processes`.

## General Metric Semantic Conventions

The following semantic conventions aim to keep naming consistent. They
Expand Down

0 comments on commit 4bc38ce

Please sign in to comment.