​
Overview

Rootly’s round robin feature introduces a streamlined way to manage escalation policies by automatically rotating the paging responsibilities among on-call team members. This ensures that alerts are distributed evenly and efficiently, reducing the burden on any single individual. This feature is included out-of the box and is available for use today.

​
Key Features

​
Paging Methods

​
Alert-Based Paging

This is the most common style of round robin paging. Incoming alerts are cycled through the rotation of users. For example, the first incoming will page User A, if User A doesn’t respond, it will escalate to level 2. The next incoming alert will page User B to ensure even distribution of alerts.

​
Cycle-Based Paging

The cycle-based feature ensures each user in the escalation level is paged in sequential order before escalating to the next level.

​
Dynamic Updates

Rootly’s web UI dynamically updates to show the current pageable person and the order of escalation. Timeline events also indicate the strategy used for each page.

​
Configuring Round Robin

  1. Navigate to Escalation Policies:
    • Go to the escalation policies section in your Rootly dashboard.
    • On-Call —> Escalation Policies
  2. Create/Select an Escalation Policy:
    • Create a new escalation policy or choose an existing policy you want to configure for round robin.
  3. Enable Round Robin:
    • When the feature flag for round robin is enabled, toggle the round robin option in each escalation policy level.
  1. Select either Alert-Based or Cycle-Based Paging:
    • Set the levels to be alert-based, where each new alert pages the next person in line.

​
Example Scenario (Alert-based)

In this example, we have an escalation policy named “SRE - Round Robin EP” with one round robin alert-based level. The first pageable person is Alexandra. When alert A comes in, if Alexandra doesn’t respond within five minutes, the alert moves to Andre, and then to Purvai.
  • When alert B comes in, it will then go to Shadab and then escalate to the next level.
  • When alert C comes in, it will then go to Andre and then escalate to the next level.
  1. Initial Alert:
    • Alexandra receives the first alert.
  2. Escalation to Next Person:
    • After five minutes without a response, the alert escalates to Andre.
  3. Further Escalation: If Andre also doesn’t respond, the alert moves to Purvai.
  4. Repeat Cycle:
    • The repeat feature cycles the alerts back to Alexandra after Purvai.

​
Example Scenario (Cycle-Based)

In this example, we have an escalation policy named “SRE - Round Robin EP” with one cycle-based level. The first pageable person is Alexandra. When alert A comes in, it will first go to Alexandra and if she does not respond, then the alert moves to Shadab, and then to Andre.
  1. Initial Alert:
    • Alexandra receives the first alert.
  2. Escalation to Next Person:
    • After one minute without a response, the alert escalates to Shadab.
  3. Further Escalation:
    • If Shadab also doesn’t respond, the alert moves to Andre.
  4. Repeat Cycle:
    • The repeat feature cycles the alerts back to Alexandra after Andre.

​
Timeline Events

Timeline events will now show an indication of the strategy used for each page, providing clarity on how the alert was escalated and which strategy was employed.