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
We use gRPC to communicate between microservices written in NestJs (see: https://docs.nestjs.com/microservices/grpc). Similar to HTTP communication, we explicitly throw RpcExceptions with a status code for different types of handled exceptions. Since these are not unexpected exceptions, they should not be captured by Sentry.
Hey, thanks for writing in! This definitely makes sense. I have added the issue to the nest tracking issue and will try to have a look in the coming weeks.
`RpcExceptions` are always explicitly thrown in nest. Therefore, they
are expected for users and should not be sent to Sentry.
This PR filters these exceptions. In `@sentry/nestjs` we can simply use
`instanceof RpcExceptions` to achieve this. In `@sentry/node` we do not
have access to this class, so we need to check based on a property.
[ref](#13190)
Problem Statement
We use gRPC to communicate between microservices written in NestJs (see: https://docs.nestjs.com/microservices/grpc). Similar to HTTP communication, we explicitly throw RpcExceptions with a status code for different types of handled exceptions. Since these are not unexpected exceptions, they should not be captured by Sentry.
Solution Brainstorm
Similar to filtering HttpExceptions (#13064), it would be advisable to filter out RpcExceptions as well, because they are thrown explicitly (see: https://docs.nestjs.com/microservices/exception-filters).
The text was updated successfully, but these errors were encountered: