> 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.md). # Alerting - [Overview](https://docs.ilert.com/alerting/overview.md): How ilert turns events from your tools into alerts, and how alerts reach the person who can do something about them. - [How ilert processes events & alerts](https://docs.ilert.com/alerting/overview/understanding-event-flows.md): What happens to an event between your tool sending it and someone being notified, in the order ilert applies each check, and where every setting takes effect. - [Data retention](https://docs.ilert.com/alerting/overview/data-retention.md): How long ilert retains customer data, including alerts, logs, configuration data, and the timelines that apply when an account is deleted. - [ilert sender IDs, domains and IPs](https://docs.ilert.com/alerting/overview/phone-numbers.md): Add ilert phone numbers to white lists, ensuring voice alerts reach the responders at the right time. ilert's sender IDs used for outgoing notification (e.g., SMS phone numbers, caller IDs, etc.). - [SMS and voice alerts in China](https://docs.ilert.com/alerting/overview/phone-numbers/sms-and-voice-alerts-in-china.md): You may find information regarding ilert voice and SMS alerts for Chinese landline and mobile devices below. - [Working with alerts](https://docs.ilert.com/alerting/working-with-alerts.md): Filter the alert list down to what you care about, save those views, and act on alerts in bulk. - [Alert view](https://docs.ilert.com/alerting/working-with-alerts/alert-view.md): One alert on one page: its status, who is responding, the events behind it, and every action you can take on it. - [Merging alerts](https://docs.ilert.com/alerting/working-with-alerts/merging-alerts.md): The Alert Merge feature lets you combine multiple existing alerts into a single main alert. It's designed to help teams reduce noise and consolidate duplicate alerts. - [Alert source logs](https://docs.ilert.com/alerting/working-with-alerts/alert-source-logs.md): Inspect the raw events an alert source received, and what ilert did with each one. - [Dashboard](https://docs.ilert.com/alerting/working-with-alerts/dashboard.md): Build pages of widgets for open alerts, who is on call, open incidents, service health and metrics, and choose who can see and change them. - [Configure alerting](https://docs.ilert.com/alerting/configure-alerting.md): Connect your tools, decide which events deserve a page, and control when and how responders are notified. - [Alert sources](https://docs.ilert.com/alerting/configure-alerting/alert-sources.md): Connect a tool to ilert, then decide what its events mean: who gets paged, how urgent it is, and which events are worth an alert at all. - [Intelligent alert grouping with ilert AI](https://docs.ilert.com/alerting/configure-alerting/alert-sources/using-ilert-ai-for-alert-grouping.md): Group events into an open alert by what they say rather than by their alert key, choose the grouping window, and tune the similarity threshold. - [Support hours](https://docs.ilert.com/alerting/configure-alerting/support-hours.md): Define support hours to set an alert's priority by whether it arrives in or out of the hours your team covers. - [Maintenance windows](https://docs.ilert.com/alerting/configure-alerting/maintenance-windows.md): Stop planned work from paging anyone, and tell your subscribers about it before it starts. - [Notification settings](https://docs.ilert.com/alerting/configure-alerting/notification-settings.md): How ilert reaches you: the contacts it can use, the channels you have activated, and the rules that decide which one fires when. - [Mute notifications](https://docs.ilert.com/alerting/configure-alerting/notification-settings/mute-notifications.md): Silence every ilert notification channel for a set period — a night off, a flight, a holiday. - [Event flows](https://docs.ilert.com/alerting/configure-alerting/event-flows.md): A routing layer in front of your alert sources: branch on the payload, wait for business hours, and send each event to the source that suits it. - [Heartbeat monitoring](https://docs.ilert.com/alerting/heartbeat-monitoring.md): Alert on silence: a heartbeat monitor expects a ping at a fixed interval and raises an alert through an alert source when one does not arrive. - [Prometheus heartbeat example](https://docs.ilert.com/alerting/heartbeat-monitoring/prometheus-heartbeat-example.md): Monitor the liveness of your Prometheus and Alertmanager stack with an always-firing alert that pings an ilert heartbeat monitor. - [CLI heartbeat examples](https://docs.ilert.com/alerting/heartbeat-monitoring/cli-heartbeat-examples.md): Ping an ilert heartbeat monitor from a shell, a backup script, or a cron job, so that only a successful run counts as a sign of life. - [Email heartbeat example](https://docs.ilert.com/alerting/heartbeat-monitoring/email-heartbeat-example.md): Ping a heartbeat monitor by email when the monitored system cannot make outbound HTTPS requests but can still send mail. - [Deployment events](https://docs.ilert.com/alerting/deployment-events.md): Deployment events put recent changes on the alert, so a responder opens a page that already answers what changed just before this fired. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ilert.com/alerting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.