Source
Incident response, status pages & post-incident review — found from sitemap — ilert
Checked for ilert on 6 Nov 2026
- Page
- https://docs.ilert.com/incidents-and-status-pages/incidents/declare-an-incident
- Checked
- 6 Nov 2026, 04:34 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:88298b675a8a45e4f6e01fbeda7415ebe47a16a8e82ac0bb82b909a8de662868
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Incident declare sources Report an error
“Declare an incident from scratch or from an alert, and link the alerts that led to it.”
-
Incident declared status Report an error
“Either way it opens in the Declared status, ready to coordinate.”
-
Incident required fields Report an error
“Only Title and Severity are required, and severity is already filled in.”
-
Incident default severity Report an error
“The business impact. Defaults to SEV3”
-
Incident templates Report an error
“Fills Title, Summary, and Severity from a saved incident template. It never ticks Create incident channel for you”
-
Incident summary AI draft Report an error
“What is known so far. ilert AI can draft it from the title”
-
Incident affected services suggestions Report an error
“The services being impacted, each with an impact level. ilert suggests candidates”
-
Incident channel high severity Report an error
“Choosing SEV1 or SEV2 ticks Create incident channel for you. It is a default, not a rule”
-
Declare from alert prefill Report an error
“the title comes from the alert title; the summary is drafted from the alert details; affected services are pre-selected from the alert's related services, and you set each impact level; the alert is linked, and its responders become responders on the incident.”
-
Alert escalation continuation Report an error
“An escalation still running on that alert is continued on the incident rather than dropped, so nobody who was already being paged is lost.”
-
Link alert accepts Report an error
“accepts it, if it was still pending — which is what stops its escalation, because an accepted alert has an owner;”
-
Alert single incident Report an error
“An alert belongs to at most one incident. Linking one that is already linked fails with an error rather than moving it.”
-
Unlink behavior Report an error
“It goes back to showing Accepted — the status it has had all along, behind the Linked label — and nothing else changes. In particular its escalation does not restart”
-
Resolve checklist Report an error
“It opens the Before you resolve checklist, where closing each linked alert is offered and ticked by default.”
-
Impact levels Report an error
“Affected services record which business capabilities are being hit, each at an impact level such as Degraded or Major outage.”
-
Status update required for public Report an error
“A service's public status moves only when you post a status update.”
Scores citing this record
- The Engineering Manager Incident response, status pages & post-incident review
- The ICT Risk Officer Incident response, status pages & post-incident review
- The IT Operations Manager Incident response, status pages & post-incident review
- The MSP NOC Lead Incident response, status pages & post-incident review
- The Skeptic Incident response, status pages & post-incident review
- The SRE Lead Incident response, status pages & post-incident review