With dozens of open incidents there's no way to narrow the list. Add severity chips (as on Hosts), a source filter (hosts, clusters, certificates, Cloudflare, Akamai, checks ...) and a text box. Keep the filter in the URL so a link can be shared.
With dozens of open incidents there's no way to narrow the list. Add severity chips (as on Hosts), a source filter (hosts, clusters, certificates, Cloudflare, Akamai, checks ...) and a text box. Keep the filter in the URL so a link can be shared.
Done in #60. The Alerts page now has severity chips (critical, serious, warning) and chips for where the problem is (hosts, clusters and VMs, certificates, checks, mail, data layer, backups, Cloudflare, Akamai), each with its count of open incidents, plus a text box. Both lists, open and recently resolved, follow them, and the address keeps them, e.g. /alerts?severity=critical&source=clusters&q=prod. GET /api/v1/incidents gives each incident its source.
Done in #60. The Alerts page now has severity chips (critical, serious, warning) and chips for where the problem is (hosts, clusters and VMs, certificates, checks, mail, data layer, backups, Cloudflare, Akamai), each with its count of open incidents, plus a text box. Both lists, open and recently resolved, follow them, and the address keeps them, e.g. `/alerts?severity=critical&source=clusters&q=prod`. `GET /api/v1/incidents` gives each incident its `source`.
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.
With dozens of open incidents there's no way to narrow the list. Add severity chips (as on Hosts), a source filter (hosts, clusters, certificates, Cloudflare, Akamai, checks ...) and a text box. Keep the filter in the URL so a link can be shared.
Done in #60. The Alerts page now has severity chips (critical, serious, warning) and chips for where the problem is (hosts, clusters and VMs, certificates, checks, mail, data layer, backups, Cloudflare, Akamai), each with its count of open incidents, plus a text box. Both lists, open and recently resolved, follow them, and the address keeps them, e.g.
/alerts?severity=critical&source=clusters&q=prod.GET /api/v1/incidentsgives each incident itssource.