Hang on, I already use Sentry
Keep @sentry/node. 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 more to a failed request than a 500. The Sentry Express integration sends the exception behind it to your Telebugs server.
Space pauses or resumes. R replays. Escape shows the complete setup.
Keep @sentry/node. 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.
No. The Sentry error handler connects Express request errors to Telebugs. You can also report an error explicitly when your route handles it and carries on.
Yes. Add the browser SDK or your frontend framework’s integration. Keep both sides’ reports on the same Telebugs server.