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.
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.
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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.