Configure alerting

Connect your tools, decide which events deserve a page, and control when and how responders are notified.

Configuring alerting is mostly a question of noise. Every tool you connect can page someone; the settings in this section decide which signals are worth waking a person for, and which should be grouped, downgraded, or dropped.

Start with an alert source. Everything else is optional refinement.

Where each setting belongs

Most alerting behavior is configured on the alert source itself — filtering, grouping, templates, priority, and which escalation policy to use. Reach for the other objects when the alert source alone cannot express what you need.

Reach for	When	Plan
Alert sources	Always. This is where events arrive and where most noise is controlled.	Free, though several settings on it are gated
Support hours	Off-hours pages should be quieter, but not silent.	Scale
Maintenance windows	Planned work will generate alerts nobody needs to see.	Free
Event flows	Routing depends on conditions, needs a delay, or needs the payload transformed before it reaches a source.	Scale, in beta
Notification settings	You are changing how you are reached, rather than what gets alerted.	Free

Support hours downgrade, they do not suppress.

Outside the hours you define, ilert creates LOW priority alerts rather than withholding them. A LOW alert uses only the first escalation rule and never advances past it. Real silence lives in each responder's notification rules, or in an event flow branch that drops the event.

In this section

Alert sources

Connect a tool, then control filtering, grouping, templates, and priority.

Support hours

Downgrade alerts raised outside the hours your team covers.

Maintenance windows

Suppress alerting for planned work, on specific sources and services.

Notification settings

Per-user channels and rules: what reaches you, on which device, and when.

Event flows

A routing layer above alert sources, for conditions, delays, and transforms.