You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 }
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: