Search code examples
javaspring-bootloggingsentry

Sentry.io doesn't capture errors when Spring Boot running in production?


There is Spring Boot application that runs on the server without exposing to external world. I connected Sentry to monitor it but never got any errors, even I have tons of them in the logs.

By without exposing to external world I mean that there is no open url that everyone can use for API connection.

How should I configure Sentry in order to get errors? Should I fall down to other scenarios, not default Spring Boot app configuration?


Solution

  • I fight with this problem for some time but it seems that either some of error messages were lost on the way or Sentry.io default configuration for Spring Boot sends messages with low threshold, so 1 error message for several actual errors.

    In the end, it fixed itself.