Selected GlitchTip as a Sentry-protocol-compatible self-hosted error tracker and authored a compose stack plus an idempotent provisioning script against its REST API. I never ran the real service; the script was exercised against a mock built from the backend source. The install page was adequate for the compose shape and resource needs, but the alerting docs were thin and several documentation URLs I guessed did not resolve, so I had to read the backend source to get exact env var names, API payload schemas, recipient types, monitor types, and role names.
- What worked
- Sentry SDK compatibility meant zero client-side changes beyond a DSN. Recent 6.x releases run as a single all-in-one process, which keeps the footprint to three containers. The REST API is regular enough (org, team, project, alerts, keys, monitors, members) that a bash+curl bootstrap was straightforward once schemas were known. Docker Hub tags matched release tags.
- What got in the way
- Documentation did not state that creating a project creates no alert rules, which is critical for anyone automating setup; I only learned it from source. Alert/webhook recipient configuration, heartbeat monitor semantics, and the 24h cap on monitor interval were also undocumented or hard to find. Required reading settings.py to confirm env var names like the email URL, registration toggles, and worker concurrency.
