Source
On-call schedules, rotations & escalation — found from sitemap — ilert
Checked for ilert on 6 Nov 2026
- Page
- https://docs.ilert.com/on-call-management-and-escalations/escalation-policies
- Checked
- 6 Nov 2026, 04:33 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:76e32831e7e7ac3b46b67e703443b8967f40273a30f9bc04dbddd3886795a06a
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Escalation policy purpose Report an error
“Define escalation policies in ilert to guarantee that alerts are delivered through various channels until acknowledged or resolved.”
-
Escalation rule targets Report an error
“A target: an individual user, a team or a schedule. If the target is a schedule, the user on-call at the time of the alert assignment will be added as a responder to an alert.”
-
No coverage behavior Report an error
“If an alert occurs during a time with no coverage in your schedule, then the alert will be escalated immediately to the next escalation level, without waiting for the escalation timeout.”
-
No oncall behavior Report an error
“If no one is on-call on the entire escalation policy, no one will be notified.”
-
Escalation timeout Report an error
“An escalation timeout: the amount of time that a responder has to accept an alert until it is automatically escalated to the next escalation level.”
-
Multiple targets per level Report an error
“A single escalation level can hold several targets, and they are all notified at once. How many depends on your plan; the limit is shown inline on the escalation rule when you edit the policy.”
-
Delayed escalation Report an error
“With delayed escalation, you can delay escalation by a set period of time (up to 15 minutes). That way, you can avoid getting paged for alerts that quickly resolve themselves.”
-
Routing key Report an error
“An escalation policy's routing key can be used in the Events API to overwrite an alert source's escalation policy and route alerts dynamically based on the escalation policy's routing key.”
-
Multiple routing keys Report an error
“You can define multiple routing keys in an escalation policy by separating them with commas in the routing key field. The Events API also accepts multiple routing keys in the routingKey field when separated by commas and evaluates them from left to right.”
-
Routing key template Report an error
“You can also extract the routing from the alert payload using a routing key template.”
-
Policy team assignment Report an error
“Give it a name and optionally assign the policy to a team.”
Scores citing this record
- The Engineering Manager On-call schedules, rotations & escalation
- The ICT Risk Officer On-call schedules, rotations & escalation
- The IT Operations Manager On-call schedules, rotations & escalation
- The IT Operations Manager Alert delivery, routing & noise reduction
- The MSP NOC Lead On-call schedules, rotations & escalation
- The Skeptic On-call schedules, rotations & escalation
- The SRE Lead On-call schedules, rotations & escalation