> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/alerting/configure-alerting.md). # Configure alerting 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 | | ------------------------- | ---------------------------------------------------------------------------------------------------------- | | **Alert sources** | Always. This is where events arrive and where most noise is controlled. | | **Support hours** | Off-hours pages should be quieter, but not silent. | | **Maintenance windows** | Planned work will generate alerts nobody needs to see. | | **Event flows** | Routing depends on conditions, needs a delay, or needs the payload transformed before it reaches a source. | | **Notification settings** | You are changing how *you* are reached, rather than what gets alerted. | {% hint style="warning" %} **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. {% endhint %} ## In this section
Alert sourcesConnect a tool, then control filtering, grouping, templates, and priority./pages/J3y3tEP563wQvwa27nO1
Support hoursDowngrade alerts raised outside the hours your team covers./pages/rybDspD7Tr2nlx9r9XnJ
Maintenance windowsSuppress alerting for planned work, on specific sources and services./pages/VGeT4RscHkVyKc4CMCle
Notification settingsPer-user channels and rules: what reaches you, on which device, and when./pages/vKzgTehGca500o6Nf9md
Event flowsA routing layer above alert sources, for conditions, delays, and transforms./pages/sgZh9ufiD4eSo8ogFbaQ
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ilert.com/alerting/configure-alerting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.