Incidents

Phase 2

Normalised monitoring alerts (Zabbix, Cloud Eye, Nagios, ELK) with correlation clustering.

Not built yet

This page is on the roadmap. Below is what already works that covers the same job.

What you can do today

The data model is in place — alerts land in the `alerts` table when webhook ingest is wired. Until then, the agent surfaces service outages via the Service health grid (read from service_status.json) and creates tickets for caller-reported issues.

For correlated alerts in production today, check your monitoring console directly.

Target availability

Phase 2 — once the alert ingestion webhook + correlation cron land.