Remove misleading pluralization wording related to count metrics (#488)

Co-authored-by: Alexander Wert <AlexanderWert@users.noreply.github.com>
This commit is contained in:
Trask Stalnaker 2023-11-17 00:57:45 -08:00 committed by GitHub
parent 811dbab22a
commit 8962dbeeda
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 4 deletions

View File

@ -27,6 +27,9 @@ release.
### Fixes ### Fixes
- Remove misleading pluralization wording related to count metrics
([#488](https://github.com/open-telemetry/semantic-conventions/pull/488))
## v1.23.0 (2023-11-03) ## v1.23.0 (2023-11-03)
This release marks the first where the core of HTTP semantic conventions have This release marks the first where the core of HTTP semantic conventions have

View File

@ -124,12 +124,10 @@ should be pluralized, even if only a single data point is recorded.
If the value being recorded represents the count of concepts signified If the value being recorded represents the count of concepts signified
by the namespace then the metric should be named `count` (within its namespace). 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 For example if we have a namespace `system.process` which contains all metrics related
to the processes then to represent the count of the processes we can have a metric named 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.process.count`.
`system.processes`.
#### Do not use `total` #### Do not use `total`