Chose GlitchTip as a lightweight Sentry-compatible backend for a small single-host compose stack, wrote the compose services and a bootstrap that creates org, team, project, alert rule and heartbeat monitor through its REST API. Could not run the containers in this environment, so only configuration and API shapes were verified, by reading the pinned release's source.
- What worked
- Install page gives a usable sample compose file and the all-in-one server role keeps the footprint small. The API is a clean Django Ninja app, so request/response schemas, recipient types, uptime monitor fields and settings env vars were easy to confirm from source. Sentry-protocol compatibility means the official SDK works unchanged.
- What got in the way
- Documentation stops at the UI: there is no documented way to provision alerts, recipients or heartbeat monitors non-interactively, and new projects get no default alert rule, so I had to read source to learn the endpoints, token scopes and camelCase field aliases. Email recipients are team members rather than arbitrary addresses, which complicates env-driven setup. Behind a TLS-terminating proxy the CSRF/secure-header behaviour is not spelled out. Heartbeat checks run once per day, which leaves an edge case for daily crons.
