Why is Sentry logging an error even though the exception has been caught by Symfony? #1006
-
|
We are currently investigating why our sentry logs are spammed with non-relevant errors like 4xx HTTP ones, and we discovered that the Sentry Symfony package actually log some errors even though the framework catches the exceptions - and translate them into proper HTTP responses. Does it mean that sentry logs the errors before the framework has a chance to catch them? If so, how can we prevent that? It does not make sense to add some ignored exceptions (through Can someone help us understand the unexpected behavior of Symfony Sentry? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
Hi! While they might not act semantically like regular exceptions, they are still exceptions and will produce an Instead of having a list of |
Beta Was this translation helpful? Give feedback.
Hi! While they might not act semantically like regular exceptions, they are still exceptions and will produce an
ExceptionEvent, which Sentry will capture using the ErrorListenerInstead of having a list of
ignore_exceptions, you can also inspect the events in the before_send callback and drop those events there.