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
metrics: grpc_server_status label missing for grpc server latency metric #7045
Comments
Hi @famarting / @artursouza , Can I take up this issue? |
Sure thing, I've assigned you |
Yes, of course. Thank you 😄 |
@jerinthomas1404 Are you still working on the issue? |
Got busy with some other task |
No worries! I was just curious if this was up for grabs. 😅 |
Can I take up this issue? |
👋 @ckcd, my apologies but I can't perform this action for you because your username is not in the allowlist in the file |
In what area(s)?
/area runtime
What version of Dapr?
edge: b6540a1
Expected Behavior
if the label
grpc_server_status
is expected to be included in the grpc server latency metric, it should be properly recorded and returned by the prometheus metrics format.Actual Behavior
the grpc metric
grpc.io/server/server_latency
uses the labelgrpc_server_status
when recording data, but it does not actually define that label, resulting on the label actually not being exposed in the prometheus format.Looking at the code, the current behavior is either the expected one or this has been a small mistake that no one has ever noticed:
Here we can see the metric is defined but the status label is not included https://github.com/dapr/dapr/blob/master/pkg/diagnostics/grpc_monitoring.go#L119
However, here https://github.com/dapr/dapr/blob/master/pkg/diagnostics/grpc_monitoring.go#L158 we can see that when recording data the label is passed
Steps to Reproduce the Problem
Release Note
RELEASE NOTE:
FIX missing grpc_server_status label on dapr_grpc_io_server_server_latency metric
The text was updated successfully, but these errors were encountered: