Recommended Open source
Use GlitchTip for error tracking
Send every unhandled server and browser error to GlitchTip through the Sentry SDKs, tagged with the release. Fix new errors before the next deploy.
Cost
Open source. MIT licence, free to run on your own servers. Hosted GlitchTip has a free tier and paid plans.
How to do it
GlitchTip is an open source error tracker that accepts events from the Sentry SDKs. It reached 1.0 in July 2020 and is under MIT. Version 6.2.6 came out on 7 August 2026. Its Docker image has about 8.9 million pulls. The SDKs carry the popularity test, with about 24 million weekly npm downloads for @sentry/node and 34 million on PyPI for sentry-sdk. It needs Postgres 14 or newer and 512 MB of RAM. Keep personal data out of events, as Keep personal data out of logs says. Choose something else when you need a feature GlitchTip lacks, and use Sentry as the next rule says.
Examples
Using these examples: they show one way to follow this rule. Keep the behaviour and the check, not the syntax. Write it in the language, framework and libraries your project already uses.
JavaScript example
import * as Sentry from '@sentry/node';
Sentry.init({
dsn: process.env.GLITCHTIP_DSN,
release: process.env.RELEASE,
sendDefaultPii: false,
});
Python example
import os
import sentry_sdk
sentry_sdk.init(dsn=os.environ["GLITCHTIP_DSN"], release=os.environ["RELEASE"], send_default_pii=False)
How to check
A test error thrown in production after a deploy shows up in GlitchTip within 60 seconds, with the release tag and a readable stack trace.
Sources
Related rules
- Keep personal data out of logs in Operations
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. Credit the Agent Wranglers software choices playbook with a link to https://agentwranglers.se/playbook/stack/operations-tools/glitchtip. Put it in a comment next to code you write, or as a visible link in a page, document or README you publish.