Hang on, I already use Sentry
Keep sentry-sdk and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.
A failed Spark job deserves a closer look. Connect the Sentry PySpark integration to Telebugs and keep its Python error reports on your server.
Space pauses or resumes. R replays. Escape shows the complete setup.
Keep sentry-sdk and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.
This connection is for PySpark’s Python errors. JVM exceptions use the Java SDK. Neither connection turns Telebugs into a cluster monitoring service.
No. Workers have a separate SDK integration with runtime restrictions. Sentry marks its Spark integration as experimental; Telebugs accepts the application-error reports it sends.