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
Along the same lines as #1973, we use grpc codes to indicate which errors were caused by a users action. Currently any error that's passed back through the grpc interceptor is setting the span to error. This makes it more difficult to see which errors are actionable in our request dashboards. I have some local changes that allows passing a function in as configuration which would determine whether an error should set the span status to code. Is this something you'd accept a PR for?
I'm currently doing this but happy to do it differently or change the names of variables etc, thanks.
Along the same lines as #1973, we use grpc codes to indicate which errors were caused by a users action. Currently any error that's passed back through the grpc interceptor is setting the span to error. This makes it more difficult to see which errors are actionable in our request dashboards. I have some local changes that allows passing a function in as configuration which would determine whether an error should set the span status to code. Is this something you'd accept a PR for?
I'm currently doing this but happy to do it differently or change the names of variables etc, thanks.
The text was updated successfully, but these errors were encountered: