> 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/incidents-and-status-pages.md). # Incidents & status pages - [Getting started](https://docs.ilert.com/incidents-and-status-pages/getting-started.md): Coordinate your response to an incident, and communicate it to the people who depend on you — while keeping the two apart. - [Services](https://docs.ilert.com/incidents-and-status-pages/services.md): A service is the business capability your users care about. Alerts attach to it, incidents name it, status pages publish it, and people subscribe to it. - [Service topology](https://docs.ilert.com/incidents-and-status-pages/service-topology.md): Visualize how your services depend on one another and understand the impact of an outage with the Service Health map, reconstructed automatically from your OpenTelemetry traces. - [Telemetry sources](https://docs.ilert.com/incidents-and-status-pages/service-topology/telemetry-sources.md): Connect your services to ilert by pushing OpenTelemetry traces to a telemetry source. ilert extracts the service dependencies from your traces and builds your live service topology. - [Incidents](https://docs.ilert.com/incidents-and-status-pages/incidents.md): An incident is the coordination record above your alerts: who is responding, what is known, what has been tried, and what customers have been told. - [Declare an incident](https://docs.ilert.com/incidents-and-status-pages/incidents/declare-an-incident.md): Declare an incident from scratch or from an alert, and link the alerts that led to it. - [Responders and paging](https://docs.ilert.com/incidents-and-status-pages/incidents/responders-and-paging.md): Bring people onto an incident, see who has actually joined, and name whoever is running it. - [Incident timeline and comments](https://docs.ilert.com/incidents-and-status-pages/incidents/incident-timeline-and-comments.md): The running record of an incident: what ilert logged, what your team wrote down, and what was said publicly. - [Incident channels](https://docs.ilert.com/incidents-and-status-pages/incidents/incident-channels.md): Connect a Slack, Microsoft Teams, or Google Chat channel to an incident in ilert for real-time coordination. - [Conference bridges](https://docs.ilert.com/incidents-and-status-pages/incidents/conference-bridges.md): Attach a live call to an incident in ilert so responders can jump straight into a conference bridge from the incident, the timeline, and their page. - [Postmortems](https://docs.ilert.com/incidents-and-status-pages/incidents/postmortems.md): A postmortem is a document ilert drafts from the incident and you finish, keeps beside it, and can publish to your status pages. - [Status updates](https://docs.ilert.com/incidents-and-status-pages/status-updates.md): A status update is the public half of an incident: the message your customers read, written deliberately and published when you decide. - [AI status update generation](https://docs.ilert.com/incidents-and-status-pages/status-updates/ai-status-update-generation.md): Let ilert AI draft the message of a status update, and guess which services it should name. - [Incident templates](https://docs.ilert.com/incidents-and-status-pages/status-updates/incident-templates.md): Saved wording you can apply when posting a status update, declaring an incident, or scheduling a maintenance window. - [Status pages](https://docs.ilert.com/incidents-and-status-pages/status-pages.md): Create a status page, put it on your own domain, and let it update itself from the services behind it. - [Status page layout](https://docs.ilert.com/incidents-and-status-pages/status-pages/status-page-layout.md): Customize your status page's appearance, organize services into groups, select embed options for your website, and use the announcement bar to share important updates. - [Public vs private status pages](https://docs.ilert.com/incidents-and-status-pages/status-pages/public-vs-private-status-pages.md): Compare public vs private status pages in ilert to determine which audience gets visibility into incident updates and maintenance notices. - [Audience-specific status page](https://docs.ilert.com/incidents-and-status-pages/status-pages/audience-specific-status-page.md): Create audience‑specific status pages in ilert tailored to different stakeholder groups with custom branding and messaging. - [Metrics](https://docs.ilert.com/incidents-and-status-pages/metrics.md): Numbers on a status page. A metric turns "is it up?" into "here is how it is actually performing", for anybody who can read the page. - [Import metrics from Datadog](https://docs.ilert.com/incidents-and-status-pages/metrics/import-metrics-from-datadog.md): Point a metric at a Datadog query and ilert fetches the data, so a number you already watch internally can appear on your status page. - [Import metrics from Prometheus](https://docs.ilert.com/incidents-and-status-pages/metrics/import-metrics-from-prometheus.md): Point a metric at a PromQL query and ilert fetches the data, so a number you already watch internally can appear on your status page. --- # 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/incidents-and-status-pages.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.