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

Cited by

Facts read from this source

• Escalation policy definition Report an error

  “An escalation policy is a custom set of rules for incident alerting, ideal for creating advanced incident alerting processes. It defines who will be alerted and in what order, continuing until the incident is acknowledged.”

• Alerting targets Report an error

  “Specific team members Current on-call team Slack or Microsoft Teams integrations Zapier and Webhook integrations AI SRE, which investigates the incident”

• Severities customizable Report an error

  “Severities are customizable and allow for preset alerting methods applicable across multiple escalation policies. Severities require at least one escalation policy, so create your policy first.”

• Time based rules Report an error

  “Specify conditions to stop the escalation policy or escalate to another policy at specific times.”

• Delay configuration Report an error

  “Set a time delay using Wait for [ ] minutes before escalating to. The alerting flow will begin after the defined period.”

• Metadata based rules Report an error

  “Use metadata to define custom notification flows. This allows incidents to be routed based on metadata like severity or ownership, providing greater flexibility.”

• Instructions todo list Report an error

  “Insert a custom text with a list of tasks as a comment into the incident timeline automatically. This allows you to share a specific set of instructions or links, providing immediate context for on-call.”

• Multi step policy Report an error

  “+ Escalate & alert to alert another schedule, team member, or integration if the previous step is not acknowledged.”

• Repeating policy Report an error

  “Set what happens when the policy runs out of steps at the bottom of the editor: If no one acknowledges, choose don't repeat or how many times to repeat, then escalate to a fallback policy.”

• Assignment scope Report an error

  “Creating an escalation policy does not apply it on its own. You need to assign it to the monitors, heartbeats, or integrations whose incidents it should handle.”

• Bulk assignment Report an error

  “Select the monitors you want in the monitors list, then choose Configure on-call escalation from the bulk actions and pick your policy.”

• Default behavior without policy Report an error

  “It notifies the current primary on-call by e-mail, escalates to the rest of the team if the incident is not acknowledged, and triggers all of your integrations.”

• API documented Report an error

  “Incidents API Getting an API token Pagination Monitors Heartbeats On-call & incidents Status pages Metadata Integrations Team members Organization roles Usage Reporting”

Scores citing this record

• The Agency Developer Alerting, escalation & on-call
• The Agency Developer API, monitoring as code & team administration
• The Customer Support Lead Alerting, escalation & on-call
• The E-Commerce Operations Manager Alerting, escalation & on-call
• The E-Commerce Operations Manager API, monitoring as code & team administration
• The SaaS Platform Engineer Alerting, escalation & on-call
• The Information Security Officer Alerting, escalation & on-call
• The Skeptic Alerting, escalation & on-call