Hang on, I already use Sentry
Keep Sentry.Extensions.Logging and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.
A timer fires. A queue message arrives. A function throws. Use the Sentry .NET SDK to send the error report to your Telebugs server.
Space pauses or resumes. R replays. Escape shows the complete setup.
Keep Sentry.Extensions.Logging and change its destination to your Telebugs DSN. Your error reports stay on your server. You don’t need a Sentry account.
Yes. The Sentry logging integration connects to the isolated worker host. Exceptions logged at the configured event level can become error reports in Telebugs.
No. This connection turns selected logged errors into error reports. Telebugs is for investigating those failures, not collecting every line of function output.