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
Ever since v4.3.0 which received this update #3230 it seems all non-0 gRPC status codes are being reported as errors in datadog when they should be not. e.g. NOT_FOUND (5) or INVALID_ARGUMENT (3) are acceptable responses which are not errors.
I found that in the java version of dd-trace they allow you to configure the grpc plugin error statuses. Perhaps we need something like that.
The text was updated successfully, but these errors were encountered:
Hey, I noticed this issue is still open, and it’s also impacting us. I wanted to see if there are any updates or if additional details from our side would help. Appreciate your time and effort—let me know if we can assist in any way. Thanks!
Ever since v4.3.0 which received this update #3230 it seems all non-0 gRPC status codes are being reported as errors in datadog when they should be not. e.g.
NOT_FOUND
(5) orINVALID_ARGUMENT
(3) are acceptable responses which are not errors.I found that in the java version of dd-trace they allow you to configure the grpc plugin error statuses. Perhaps we need something like that.
The text was updated successfully, but these errors were encountered: