The on-call league: GoAlert takes flagship: oncall
Status: RULED AND EXECUTED 2026-08-21 (owner, session “apps”). Spec:
docs/superpowers/specs/2026-08-21-goalert-oncall-design.md.
The ruling
Section titled “The ruling”- A fifth league,
oncall, for paging: on-call schedules, escalation chains, and delivery that keeps going until a human acknowledges. GoAlert (github.com/target/goalert, Apache-2.0) holds it.apps/flagship/goalert/,flagship: oncall, roster row inscripts/arch-fitness.sh. - Grafana OnCall OSS is excluded: archived read-only 2026-03-24, and its SMS/phone/push depended on a Grafana Cloud connection that shut off the same day. It cannot be the estate’s pager.
- Two lanes, by design. Matrix/hookshot is the visibility lane (everything, chatty). GoAlert is the paging lane (rare, escalates). Producers feed both independently; nothing bridges one into the other.
- Plugs are catalog-app-to-catalog-app. SHC core (the notification module)
and builtins (OpenObserve) cannot present as plugs into GoAlert. Their feeds
are documented day-two operator setup in
docs/guide/operations/paging.md. - Uptime Kuma monitors stay manual (closed 2026-08-21); the
goalertplug on uptime-kuma touches only its notification providers.
Why GoAlert clears the eight bars (docs/decisions/2026-08-06-flagship-tier.md §1)
Section titled “Why GoAlert clears the eight bars (docs/decisions/2026-08-06-flagship-tier.md §1)”| bar | answer |
|---|---|
| SSO without paying | native OIDC, free (oidc.plug.yaml sets it over GraphQL setConfig) |
| zero-touch install | shc install goalert -i <pg> -i <keycloak> -i <smtp> yields admin, OIDC, email, webhook destinations, a default escalation policy; no UI step |
| one app per league | oncall is new; nothing else claims it |
| free to use | Apache-2.0; Twilio is the operator’s carrier bill, not a licence |
| lifecycle honesty | no volumes; state = integrated Postgres + dataEncryptionKey in vault; backup.yaml says so; digest-pinned image |
| estate citizenship | postgres/oidc/smtp plugs; goalert socket mints per-edge keys; vault-autogen secrets; no default creds |
| honest health | real HTTP probe on /health |
| maintained upstream | v0.34.1 (2025-10-06), 1–2 minor releases/year; ~10 months quiet at ruling time; recorded, accepted |
The socket contract, in one paragraph
Section titled “The socket contract, in one paragraph”goalert is a singleton-named socket (the contract is GoAlert’s own generic
API). data: publishes nothing secret; the integration job mints, per edge,
a GoAlert service named by the plug (name@string!) and an integration key
(keyType generic|prometheusAlertmanager|grafana), attaches the service to the
install-time shc-default escalation policy, and returns token, serviceId,
ingestPath, baseUrl, internalBaseUrl over the mint channel. Disconnect
revokes the key and RETAINS the service and its alert history (reported on the
retained-cleanup channel). Deleting alert history on disconnect is the wrong
default.
What is deliberately not here
Section titled “What is deliberately not here”Matrix bridging of GoAlert outbound; WhatsApp (no OSS pager does it; Twilio
SMS/voice is the phone path); a Kuma monitor-sync; PMM/CrowdSec plugs (phase 2,
both map cleanly: PMM via keyType: grafana, CrowdSec via its templatable
http plugin).