← All platforms

Falcon error tracking

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.

~/hoofnotes  pip install sentry-sdk
~/hoofnotes  nvim app.py
import sentry_sdk
sentry_sdk.init(
# Copy the complete Telebugs DSN, key and path included.
dsn="YOUR_TELEBUGS_DSN",
)
from hoofnotes.api import app
~/hoofnotes  gunicorn app:app

Space pauses or resumes. R replays. Escape shows the complete setup.

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.

What do I get beyond a 500?

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.

What about an error I handle myself?

It can still be worth investigating. Send it with sentry_sdk.capture_exception and keep its backtrace alongside the errors the integration captures.