Alerting

    On-Call Schedules &
    Escalation Policies

    Know who is on call, send incidents to them, and move to the next step when nobody acknowledges. Available on Business plans.

    Kostenlose Testversion startenPreise anzeigen

    Social Proof

    Tausenden vertrauen uns — bewertet auf

    Sehen Sie, was echte Nutzer über Xitoring auf den weltweit führenden Bewertungsplattformen sagen.

    SourceForge ReviewsG2 ReviewsSlashdot ReviewsProduct Hunt

    Schlüssel Funktionen

    Alles, was Sie für „On-Call Schedules &“ brauchen: Escalation Policies.

    Rotations in Layers

    Daily, weekly, or custom rotations in the schedule's time zone. Layers are checked from the top down, and each can be limited to certain days and hours.

    Read the guide

    Overrides and Cover Requests

    Put someone on call for a set window, or ask your teammates to cover. The first person to accept takes the shift.

    Holidays and Shift Reminders

    On a holiday the top layer is skipped and the next one covers. People are reminded by email and push before a shift starts and told when it ends.

    Escalation Policies

    Up to 10 steps, each with its own delay. A step can notify people, notification roles, or whoever is on call, and the policy can repeat up to 10 times.

    Read the guide

    Acknowledge and Snooze

    Acknowledging stops repeat notifications and the escalation. Snoozing pauses them for 1 to 168 hours. Recovery notifications are still sent.

    Read the guide

    Acknowledge Where the Alert Lands

    Acknowledge from the dashboard, the alert email, the Slack app, or the Microsoft Teams app, and see who did it on the incident.

    Fits the Way You Already Work

    iCal Feeds

    Subscribe to your own shifts across all schedules, or to a whole schedule, from a calendar app that supports iCal URLs.

    Handoffs That Follow Local Time

    Daily and weekly handoffs stay at the same local time in the schedule's time zone, including across daylight saving changes.

    Trigger, Server, or Group

    Attach a policy to a trigger, a server, or a group. The most specific one wins: trigger first, then server, then group.

    Häufig gestellte Fragen

    Häufig gestellte Fragen zu On-Call Schedules & Escalation Policies.

    Which plans include on-call schedules and escalation policies?
    On-call schedules and escalation policies are available on Business plans.
    How does Xitoring decide who is on call?
    An override always wins. Without one, layers are checked from the top down and the first layer with someone on call decides. On a holiday the top layer is skipped, so the next layer covers.
    What happens when someone acknowledges an incident?
    Repeat notifications stop until the acknowledgement is removed, and the escalation policy stops. Recovery notifications are still sent.
    What is the difference between acknowledging and snoozing?
    Acknowledging says someone has the incident and lasts until it is removed. Snoozing is for a set time of 1 to 168 hours and pauses repeat notifications and the escalation policy for that time.
    If a trigger, its server, and its group all have a policy, which one applies?
    The trigger's policy. A server's policy is used by triggers with no policy of their own, and a group's policy is used when neither the trigger nor the server has one.
    Can I subscribe to my shifts in my calendar?
    Yes. Create a secret iCal URL for your own shifts or for a whole schedule, and subscribe to it in your calendar app. The feed is read-only and covers 7 days back to 60 days ahead.

    Put Your Rotation Next to Your Monitoring

    Build a schedule, add it to a notification role or an escalation policy, and let incidents find whoever is on call.

    Kostenlose Testversion starten

    Entdecke weiter

    Mehr von Xitoring