PagerDuty or OpsGenie based rotations
In Pro mode, you can create PagerDuty or OpsGenie-based rotations.
We will use PagerDuty from now on - but everything applies to OpsGenie as well.
A PagerDuty-based rotation is one in which members and the user on duty are sourced directly from a PagerDuty schedule rather than Round Robin.
The main benefit is that you can rely on all the other Slack-integrated features of Round Robin without the complexity of managing cross-duty shifts in both PagerDuty and Round Robin simultaneously.
To work with PagerDuty, you first need to connect PagerDuty (or OpsGenie) to Round Robin. Please follow the instructions here.
Create a PagerDuty-bound rotation.
Let's make an example.
Let's say you have a schedule called Service X, where you manage the duty responsibility for a particular service in your organization (it's just an example - we expect your schedule to have more than one user!).
You can now create a Round Robin rotation named Service X (the name is not essential) and connect it to PagerDuty from Slack using the "Manage Integrations" feature.
- Create an empty rotation. Please don't bother adding members; everything will be managed automatically. You can still add channels or topics.
- Go to "More Actions" and choose "Manage integrations...".
If PagerDuty is unavailable or the app is not running in Pro mode, you will receive a message indicating that you cannot use this function.
- Choose PagerDuty from the dropdown and search between PagerDuty schedules directly from Slack.
- After submitting, the rotation will become a PagerDuty-bound rotation; you will not be able to edit members or groups, but you will still be able to manage other aspects, like the on-duty group or the templates (from the web app).
- After the first sync, the rotation members will match the PagerDuty schedule members, and the current user on duty in the schedule will go on duty in Round Robin as well.
The match is based on the email address. If the user list does not match, verify that the PD email addresses correspond to your users' Slack email addresses.
- If the schedule changes, the same will happen to the rotation (new members, removed members, different user on duty). The sync occurs every minute; it's not real-time.