Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Define semantics for golden metrics: throughput, duration, error rate #654

Open
justinfoote opened this issue Jun 12, 2020 · 0 comments
Open

Define semantics for golden metrics: throughput, duration, error rate #654

justinfoote opened this issue Jun 12, 2020 · 0 comments
Assignees
@justinfoote
Labels
area:api Cross language API specification issue priority:p3 Lowest priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:metrics Related to the specification/metrics directory

Comments

@justinfoote
Copy link
Member

I propose that we define a generic semantic convention for throughput, duration, and error rate metrics. I believe we could make a single semantic convention that covers most cases.

The goal would be to create guidelines regarding what metric names should be used, and possibly also regarding which labels could be used. Commonality should improve discoverability of metrics between sources like http and grpc services, MQ servers and clients, database clients, etc.
@justinfoote justinfoote mentioned this issue Jun 15, 2020
Closed
@jmacd jmacd mentioned this issue Jun 23, 2020
Merged
@jmacd jmacd added the spec:metrics Related to the specification/metrics directory label Jun 23, 2020
@carlosalberto carlosalberto added the area:api Cross language API specification issue label Jun 26, 2020
@jmacd jmacd added the release:required-for-ga Must be resolved before GA release, or nice to have before GA label Jun 29, 2020
@arminru arminru linked a pull request Jul 7, 2020 that will close this issue
Add metrics semantic conventions for timed operations #657
Closed
@carlosalberto carlosalberto added the priority:p3 Lowest priority level label Jul 24, 2020
@justinfoote justinfoote mentioned this issue Aug 6, 2020
Closed
@trask trask mentioned this issue Oct 9, 2020
Closed
@bogdandrutu bogdandrutu added release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs and removed release:required-for-ga Must be resolved before GA release, or nice to have before GA labels Oct 16, 2020
@justinfoote justinfoote mentioned this issue Oct 26, 2020
Open
@fatsheep9146 fatsheep9146 mentioned this issue Oct 9, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justinfoote justinfoote

Labels
area:api Cross language API specification issue priority:p3 Lowest priority level release:allowed-for-ga Editorial changes that can still be added before GA since they don't require action by SIGs spec:metrics Related to the specification/metrics directory
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add metrics semantic conventions for timed operations justinfoote/opentelemetry-specification
4 participants
@carlosalberto @bogdandrutu @justinfoote @jmacd