blipit

Blipit error monitoring for Python. Know your app broke before your users tell you.

Install

pip install blipit

Quick start

Call init once at startup, before the app is created. For Django, put it at the top of settings.py.

import blipit

blipit.init(key="<public key>", project=<project id>, environment="production", release="myapp@1.4.2")

Both values are on the project's Keys page at app.blipit.io. If the key or project id is empty (for example an unset environment variable), init logs a warning on the blipit logger, returns False and Blipit stays off; it never raises, so a missing key cannot stop the app from starting. Unhandled exceptions are reported on their own; Django, Flask, FastAPI, Celery, SQLAlchemy and other integrations are detected automatically.

Manual capture

blipit.capture_exception(err)
blipit.capture_message("cache miss rate above 50%", level="warning")
blipit.set_user({"id": "42", "email": "ana@example.com"})
blipit.set_tag("region", "ap-southeast-1")
blipit.capture_security("login_failed", actor=email, ip=client_ip, outcome="bad_password")

Login attempts (capture_security) need the project's secret key (init with it on the server) and the Scale plan; with the public key ingest refuses them with 403 security_needs_secret_key.

Performance

Pass traces_sample_rate=0.2 to init and requests show up on the Performance page.

Docs: https://docs.blipit.io/python

Updates

In development Blipit logs one line on the blipit logger when a newer version is out, with the reason and the command. Update with pip install -U blipit. Details: https://docs.blipit.io/updates