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
Trying to standardize metrics across our organization according to OpenTelemetry (OTel) conventions. I noticed that the standard unit for HTTP duration is in seconds (s), while that of RPC is in milliseconds (ms). I need to understand the rationale behind this difference in convention.
What did you expect to see?
Additional context.
I came across a pull request (PR) that addresses the issue for HTTP duration, changing it from milliseconds to seconds. However, I'm uncertain why RPC metrics have a different unit.
rpc.server.duration Histogram ms Measures the duration of inbound RPC. [1]
http.server.request.duration Histogram s Duration of HTTP server requests. [1]
The text was updated successfully, but these errors were encountered:
Currently, implementations emit RPC metrics in milliseconds, so changing semantic conventions would be a breaking change for those implementation. We plan to do those changes once we work on stabilizing RPC semantic conventions.
trask
transferred this issue from open-telemetry/opentelemetry-specification
Apr 2, 2024
What are you trying to achieve?
Trying to standardize metrics across our organization according to OpenTelemetry (OTel) conventions. I noticed that the standard unit for HTTP duration is in seconds (s), while that of RPC is in milliseconds (ms). I need to understand the rationale behind this difference in convention.
What did you expect to see?
Additional context.
I came across a pull request (PR) that addresses the issue for HTTP duration, changing it from milliseconds to seconds. However, I'm uncertain why RPC metrics have a different unit.
rpc.server.duration Histogram ms Measures the duration of inbound RPC. [1]
http.server.request.duration Histogram s Duration of HTTP server requests. [1]
The text was updated successfully, but these errors were encountered: