Page MenuHomePhabricator

Splunk On-Call resets overrides after changes to the escalation
Open, MediumPublic

Description

@lmata FYI today VO thought that Jaime and me were both oncall instead of the people we had swapped with. I fixed it for this week but also noticed that for all the existing overrides, the EMEA escalation routing have been unassigned. Possibly related to the May 1st batphone change for EMEA.
I didn't change the other overrides (that hence need fixing) and also wanted to brought up the issue because maybe the current procedure to put the batphone for a day might be the cause of this.

It seems the overrides were "reset" after adding back the EMEA rotation to the escalation, tracking tasks to follow up with Splunk and identify the issue/fix.

Event Timeline

lmata triaged this task as Medium priority.May 2 2024, 1:58 PM

I've run into this today, what seems to happen is the following:

  • The escalation "SRE Business Hours (Escalation)" gets modified. Not sure if removing steps or leaving the steps unmodified and changing the rotations trigger the behavior
  • If the escalation was currently in an override, then the person taking the override gets reset and noone is overriding (the override itself stays in place)