Hang on, I already use Sentry
Keep io.sentry:sentry. Point it at your Telebugs DSN and keep reporting errors as before. The reports go to your server; you don’t need a Sentry account.
There’s a story behind that exception. Keep its backtrace on your server, with the Sentry Java SDK and Telebugs.
Space pauses or resumes. R replays. Escape shows the complete setup.
Keep io.sentry:sentry. Point it at your Telebugs DSN and keep reporting errors as before. The reports go to your server; you don’t need a Sentry account.
Yes. Telebugs keeps the exception, its backtrace, and the context the SDK sends with it. You can follow the calls back through your Java code.
Yes. There are Sentry integrations for Spring and Spring Boot. They connect request error handling to the same Telebugs server.