We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I'm using UnaryServerInterceptor from "gopkg.in/DataDog/dd-trace-go.v1/contrib/google.golang.org/grpc".
UnaryServerInterceptor
"gopkg.in/DataDog/dd-trace-go.v1/contrib/google.golang.org/grpc"
This generates a metric trace.grpc.server.hits which is the main metric I have for incoming traffic for my gRPC service.
trace.grpc.server.hits
I'd expect this metric to be labeled with the gRPC status code so I can count hits by status code.
Other datadog integrations (such as python flask) already do this with http status code.
The text was updated successfully, but these errors were encountered:
Hello!
Yes, this is a known limitation; http.status_code is a tag on trace metrics but grpc.status.code is not. The grpc spans populate the latter attribute and not the former. See: https://docs.datadoghq.com/tracing/metrics/metrics_namespace/#metric-suffix
A few quick workarounds while the team discusses this further:
Sorry, something went wrong.
mtoffl01
No branches or pull requests
I'm using
UnaryServerInterceptor
from"gopkg.in/DataDog/dd-trace-go.v1/contrib/google.golang.org/grpc"
.This generates a metric
trace.grpc.server.hits
which is the main metric I have for incoming traffic for my gRPC service.I'd expect this metric to be labeled with the gRPC status code so I can count hits by status code.
Other datadog integrations (such as python flask) already do this with http status code.
The text was updated successfully, but these errors were encountered: