-
Notifications
You must be signed in to change notification settings - Fork 890
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
.count
metric naming convention only applies to UpDownCounters
#3493
Conversation
71d6af9
to
45c2c20
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.
Co-authored-by: Reiley Yang <[email protected]>
Co-authored-by: Reiley Yang <[email protected]>
@@ -114,7 +115,7 @@ 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 | |||
#### Use `count` Instead of Pluralization for UpDownCounters |
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.
Why keep this around for UpDownCounters? This section appears to include the only mentions of a metrics namespace. Getting rid this rule altogether would mean getting rid of a confusing and poorly defined concept.
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.
Oops I found namespace mentioned in the General Guidelines section as well.
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.
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.
Or maybe we decide which approach to take with the namespace, then we might not even need this? 🤔. I agree with @jack-berg I find the rules around this very confusing.
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.
I think we should address this separately. Approved and voted for #3477.
Co-authored-by: Tyler Yahn <[email protected]>
Co-authored-by: Tyler Yahn <[email protected]>
Co-authored-by: Tyler Yahn <[email protected]>
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.
LGTM
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.
This is a step in the right direction.
I'm supportive of this. I like what @jack-berg suggests, but I'm also a fan of merging this as-is and going further in the future.
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.
This PR needs to move to the Semantic Conventions repository.
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
Fixes #3457
Changes
Updates
.count
metric naming convention so that it only applies to UpDownCounters, and adds that.total
should not be used by either Counters or UpDownCounters