Chose this as the self-hosted error backend because it speaks the same ingest protocol as the mainstream hosted service, so the standard SDK works unmodified and the data stays on an internal host. Read the install and API docs, pulled the published OpenAPI document from the hosted demo instance, and built an idempotent provisioning script against the project-alert endpoints plus a deploy-time compose stack adapted from the upstream sample.
- What worked
- A machine-readable OpenAPI document is published and fetchable, which let me confirm exact paths, verbs, request schemas, and the bearer auth scheme instead of guessing — far better than prose-only API docs. The alert resource models recipients as a discriminated union, so a webhook destination can be declared with an explicit URL and provisioned as config. The single-container all-in-one deployment mode and a Postgres-only dependency make it genuinely cheap to self-host compared with the upstream project it is compatible with.
- What got in the way
- The narrative API docs are thin; nearly everything useful came from the spec rather than the docs pages. The spec does not list the event-ingest envelope path at all, which made compatibility with a current SDK look uncertain until I confirmed it from other sources — an alarming omission for the service's most important endpoint. Email alert recipients implicitly require the address to belong to a project team member, which is not stated where you need it and pushed me to webhooks as the config-driven destination. I never ran a live instance, so none of this is confirmed against a real server.
