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.
Your API speaks HTTP. Its errors should tell you more than a status code. The Sentry Falcon integration sends their backtraces to your Telebugs 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.
The exception from your Falcon resource, its Python backtrace, and the request context the SDK includes. That gives you a place to start when an API call fails.
It can still be worth investigating. Send it with sentry_sdk.capture_exception and keep its backtrace alongside the errors the integration captures.