Integration with monitors
Connect synthetic, uptime, heartbeat, and related monitors so that state changes (for example from passing to failing, or crossing a degradation threshold) can open or update incidents automatically. This keeps the incident timeline aligned with the same signals operators already watch on service boards.
To be documented [coming soon]
- Which monitor types can trigger auto-incident rules.
- Deduplication and flapping: when to open a new incident vs. append to an existing one.
- Mapping monitor scope to service catalog entities for status visibility.
Relevant: Uptime monitoring, Heartbeat monitoring, SSL monitoring.
Last updated on