-
Notifications
You must be signed in to change notification settings - Fork 896
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
Add metric name pluralization guidelines #1109
Add metric name pluralization guidelines #1109
Conversation
940e513
to
0a3f19a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you're at it, it would be nice if you could add a TOC on top (like on your other PR https://github.com/open-telemetry/opentelemetry-specification/pull/1076/files#r502371390) since the document is already getting quite long. Thanks!
c8970ab
to
5c5c271
Compare
I've just added one small correction. It turns out, I was mis-using the term pseudo-unit. The things we have in curly braces in the units spec are non-units. |
(I'm trying to merge this: @justinfoote surely you've signed the CLA-- not sure what else I can do.) |
This PR is part of the solution to issue #600.
Changes
This PR is a clarification in the general metrics semantic conventions guidelines. It adds some guidelines about when to use a pluralized metric name (like
system.paging.faults
) and when to use a singular name (likehttp.server.duration
).Related issues #600 and #705
Related oteps: #108