Scenario: Skyler creates every-other-day coverage using the Day-by-day shift type 🔗
Skyler, the site reliability engineering (SRE) manager for Buttercup Games, needs to create an on-call schedule for the checkout service SREs. To cover the checkout service Monday through Sunday and have the SREs on call every other day, Skyler wants to create two rotations:
Rotation 1: Monday, Wednesday, and Friday 24x7
Rotation 2: Tuesday, Thursday, Saturday, and Sunday 24x7
Skyler takes the following steps to configure a schedule that meets these coverage needs:
Skyler creates a new schedule for the checkout service and names it accordingly: Checkout service. Skyler adds a Checkout teams tag to make the schedule easier to find. The teams tag also sorts the list of responders so they’re easier to find and select when Skyler adds them to a shift later. The following image shows the new schedule Skyler creates with the teams tag.
Skyler creates a shift named M,W,F in the schedule for the checkout service.
Using the Day-by-day shift type, Skyler creates the every-other-day coverage they need. Day-by-day shifts are designed to span 24 hours or fewer on select days of the week and are ideal for short-term shifts that are staggered on specific days of the week, with responders rotating on a more frequent basis.
Skyler selects a shift handoff of 3, which configures the shift to assign the same responder as on call for Monday, Wednesday, and Friday. Skyler then adds the SREs as responders. The following image shows the T,R,S,U shift within the schedule for the checkout service.
Using the Schedule Preview, Skyler verifies that they configured the M,W,F shift correctly. As shown in the following image, Alex is on call Monday, Wednesday, and Friday for 24 hours, and then the next responder takes over.
Skyler creates a shift named, T,R,S,U in the schedule for the checkout service.
Using the Day-by-day shift type, Skyler creates the every-other-day coverage they need. Day-by-day shifts are designed to span 24 hours or fewer on select days of the week and are ideal for creating short-term shifts that are staggered on specific days of the week, with responders rotating on a more frequent basis.
Skyler selects a shift handoff of 4, which configures the shift to assign the same responder as on call for Tuesday, Thursday, Saturday, and Sunday. Skyler then adds the SREs as responders.
Using the Schedule Preview, Skyler verifies that they configured the T,R,S,U shift correctly. As shown in the following image, Alex is on call Tuesday, Thursday, Saturday, and Sunday for 24 hours, and then the next responder takes over.
Skyler adds the checkout schedule as the first step of the Incident workflow for the checkout service incident policy. The incident workflow that Skyler creates is shown in the following image.
With the schedule configured and added to the incident policy, Skyler enables the incident policy so that alerts begin flowing and triggering incidents that notify the responders in the newly-configured schedule.
Skyler created the every-other-day coverage they need by creating a single schedule for the checkout service with two day-by-day shifts: one shift for Monday, Wednesday, and Friday coverage and a second shift for Tuesday, Thursday, Saturday, and Sunday coverage. Skyler added the schedule to the incident workflow in the incident policy for the checkout service. Skyler then enabled the policy so that alerts begin flowing and triggering incidents that notify the responders in the newly-configured schedule.
For steps to set up an on-call schedule, see Create and manage on-call schedules.
For steps to create an incident policy, including steps for incident workflows, see Create and configure incident policies.
For a scenario with a multi-shift schedule and primary and secondary coverage, see Scenario: Skyler creates business-hours and nights-and-weekend rotations for the web application service.