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.

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

Are there semantic conventions for metrics? #518

Closed
yangd102 opened this issue Mar 18, 2020 · 2 comments
Closed

Are there semantic conventions for metrics? #518

yangd102 opened this issue Mar 18, 2020 · 2 comments
Labels
spec:metrics Related to the specification/metrics directory

Comments

@yangd102
Copy link

Are there semantic conventions for metrics? For example for backend calls (rpc, http, apis etc) could have a general metric of the form. This doesn't make much of a difference if you only do gRPC, however if there are several types of ways to do backend calls, should there be a set of lowest common denominator metrics that everyone can use?

opentelemetry.io/server/count { name, status }
opentelemetry.io/server/latency { name, status }

opentelemetry.io/client/count { name, status }
opentelemetry.io/client/latency { name, status }
@jmacd
Copy link
Contributor

jmacd commented Mar 18, 2020

Metrics should use the same semantic conventions that spans and resources do. Are there any missing conventions?

@bogdandrutu bogdandrutu added the spec:metrics Related to the specification/metrics directory label Jun 12, 2020
@bogdandrutu
Copy link
Member

Duplicate of #651

@bogdandrutu bogdandrutu marked this as a duplicate of #651 Jun 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec:metrics Related to the specification/metrics directory
Projects
None yet
Development

No branches or pull requests

3 participants