-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
stats/opentelemetry: CSM Observability server side component changes #7264
Conversation
} | ||
err := handler(srv, als) | ||
if err != nil { | ||
logger.Infof("RPC failed with error: %v", err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove this log, too, please.
I don't see why we would want to log when an RPC fails in the otel plugin. It's not really a significant event, and could become extremely spammy. If you need it for debugging then you can V(2)
it.
https://github.com/grpc/grpc-go/blob/master/Documentation/log_levels.md#info
At verbosity of 0 (the default), any single info message should not be output more than once every 5 minutes under normal operation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok I had this since every? most? interceptors I saw in the code base had this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What interceptors are those?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Examples are not library code, though, so that is fine.
RELEASE NOTES: N/A