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

metrics: grpc_server_status label missing for grpc server latency metric #7045

Closed
famarting opened this issue Oct 16, 2023 · 9 comments
Closed
Assignees
Labels
good first issue Good for newcomers kind/bug Something isn't working P1
Milestone

Comments

@famarting
Copy link
Contributor

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 label grpc_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

@famarting famarting added the kind/bug Something isn't working label Oct 16, 2023
@artursouza artursouza added this to the v1.13 milestone Oct 16, 2023
@artursouza artursouza added P1 good first issue Good for newcomers labels Oct 16, 2023
@jerinthomas1404
Copy link

Hi @famarting / @artursouza , Can I take up this issue?
I would like to contribute to dapr

@yaron2
Copy link
Member

yaron2 commented Oct 21, 2023

Hi @famarting / @artursouza , Can I take up this issue? I would like to contribute to dapr

Sure thing, I've assigned you

@famarting
Copy link
Contributor Author

Hi @famarting / @artursouza , Can I take up this issue? I would like to contribute to dapr

Yes, of course. Thank you 😄

@sp6370
Copy link

sp6370 commented Nov 20, 2023

@jerinthomas1404 Are you still working on the issue?

@mendaxjerin
Copy link

mendaxjerin commented Nov 21, 2023

@jerinthomas1404 Are you still working on the issue?

Got busy with some other task

@sp6370
Copy link

sp6370 commented Nov 21, 2023

No worries! I was just curious if this was up for grabs. 😅

@ckcd
Copy link
Contributor

ckcd commented Nov 24, 2023

Can I take up this issue?

@dapr-bot
Copy link
Collaborator

dapr-bot commented Dec 5, 2023

👋 @ckcd, my apologies but I can't perform this action for you because your username is not in the allowlist in the file .github/scripts/dapr_bot.js.

@yaron2
Copy link
Member

yaron2 commented Feb 26, 2024

Closed via #7255.

Thanks @ckcd

@yaron2 yaron2 closed this as completed Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers kind/bug Something isn't working P1
Projects
None yet
Development

No branches or pull requests

8 participants