Source

Alerting, escalation & on-call — found from sitemap — Better Stack Uptime

Checked for Better Stack Uptime on 1 Nov 2026

Technical details

type: page
http status: 200
content hash: sha256:3582ffd931d1773d8b019843f27988d080dbb555f8f6d2937d86ec26830a4fb6
permission: robots_ok
screenshot: Screenshot on file (internal exhibit, not published)

Cited by

Escalation policy reference Report an error

“you can simplify management by creating smaller reusable policies. Such a policy groups all your on-call schedules together. You can then reference this single container policy within your other escalation policies, making them cleaner and easier to manage.”
Schedule active hours Report an error

“Select Schedule active: Specific days and times and configure when the schedule should be active. No one in the schedule will be alerted outside its active hours.”
Follow the sun Report an error

“Better Stack automatically notifies whoever's on-call in their local region.”
Parallel policy triggering Report an error

“They will get started in parallel, and the main escalation policy would immediately continue. If you want to wait for the referenced policies to finish, add a waiting period to your next step.”
Escalation re alert delay Report an error

“you can re-alert the Follow-the-sun on-call policy after 15 minutes, and then escalate to the entire team if the incident is still not acknowledged.”