Alerts & triggers

Beyond notifying end users, you'll want your team to know the moment something breaks.

Per-monitor alerts

Each monitor can have alerting configured so that a change of state (for example UP → DOWN) raises a notification. Typical options include:

• Confirmation threshold — require N consecutive failing checks before alerting, to avoid flapping on a single blip.
• Recovery — notify again when the monitor returns to UP.

Triggers (notification channels)

Triggers define where alerts go. Configure them under Triggers in the console, then attach them to monitors. Common uses:

• Email your on-call address or a team distribution list.
• Webhook to a chat or incident tool, so alerts land where your team already works.

Recommended setup

1. Create a trigger for your team's channel (email or webhook).
2. Attach it to your important monitors.
3. Set a confirmation threshold (e.g. 2–3 failures) to cut false alarms.
4. Test it by temporarily pointing a monitor at an unreachable target.