-
Notifications
You must be signed in to change notification settings - Fork 164
Add metric semantic conventions for timed operations #129
Add metric semantic conventions for timed operations #129
Conversation
1405c44
to
663ac61
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.
As long as we avoid assuming a span exists when these metrics are getting generated (because one might not exist) I'm fine with this.
@open-telemetry/specs-metrics-approvers would y'all have a look at this? I'd like us to come to an agreement sooner rather than later that we want some semantic conventions about naming and labeling of metrics, and that we're not intending to specify API or SDK changes with them. |
### Naming | ||
|
||
The semantic conventions should specify the naming of this metric instrument, following | ||
the [Metric Instrument Naming Guidelines](./108-naming-guidelines.md#guidelines). |
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.
broken link?
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.
😬 Fixed.
Thanks!
Any update on this? |
@justinfoote we are marking OTEPs which are no longer being updated as |
This OTEP attempts to address open-telemetry/opentelemetry-specification#654.
I'd like us to come to agreement that we ought to have semantic conventions describing timing metrics. These semantic conventions will describe what instrument(s) are created, how they are named, and what labels are applied to them. They will not describe how or where the instruments are created and incremented.