Alerts: filter by severity, where it is and text #60

Merged
jcoffey-dev merged 2 commits from feature/alerts-filter into main 2026-11-16 06:55:23 +00:00
Owner

Severity chips, chips for where the problem is (hosts, clusters and VMs, certificates, checks, mail, data layer, backups, Cloudflare, Akamai) and a text box on the Alerts page, applied to open and recently resolved, kept in the address: /alerts?severity=critical&source=clusters&q=prod. GET /api/v1/incidents gives each incident its source. Docs: formats.md.

Closes #42.

Severity chips, chips for where the problem is (hosts, clusters and VMs, certificates, checks, mail, data layer, backups, Cloudflare, Akamai) and a text box on the Alerts page, applied to open and recently resolved, kept in the address: /alerts?severity=critical&source=clusters&q=prod. GET /api/v1/incidents gives each incident its source. Docs: formats.md. Closes #42.
jcoffey-dev added 2 commits 2026-11-16 06:45:16 +00:00
With dozens of incidents there was no way to narrow the Alerts page
(#42). It now has severity chips (critical, serious, warning), chips for
where the problem is (hosts, clusters and VMs, certificates, checks,
mail, data layer, backups, Cloudflare, Akamai) with each one's count of
open incidents, and a text box. Both lists, open and recently resolved,
follow them, and the address keeps them:
/alerts?severity=critical&source=clusters&q=prod.

GET /api/v1/incidents gives each incident its source, so scripts can
filter the same way.

Closes #42.
Alerts: test where each incident is from
ci / check (pull_request) Successful in 6m55s
ci / postgres (pull_request) Successful in 10m2s
43e3ead904
jcoffey-dev merged commit 4d3a62c7a5 into main 2026-11-16 06:55:23 +00:00
jcoffey-dev deleted branch feature/alerts-filter 2026-11-16 06:55:23 +00:00
Sign in to join this conversation.