CEOC Workflow: @ceoc-next Slack handle trial
Problem Statement
The CEOC workflow requires SE to manually search for the next on-call SE when needing to reach them before rotation schedules update.
What is the problem?
This creates delays during time-sensitive situations where quick handover or early coordination is needed.
Why is this a problem?
Current pain points:
- Wait for
@ceochandle to update after rotation - Manually search PagerDuty schedules or #spt_leaders-daily
- Time lost during emergency situations
Proposal
We are evaluating using a new slack handle @ceoc-next to keep track of the next on-call for the current CEOC shift.
These are the on-call engineers for the next two weeks. Would you kindly keep an eye on the @ceoc-next slack group and verify if you are added properly before your scheduled shifts?
This will start updating once this MR is merged.
AMER 1
AMER 2
AMER 3
APAC 1
APAC 2
EMEA 1
-
@asalii -
@cnightingale -
@rvzon -
@ckaburu -
@asmaa.hassan -
@mrjkc -
@lalabi -
@simonstreet -
@mnagle2 -
@dnldnz -
@d.israel -
@dwainaina -
@gyoachum
EMEA 2 (Some duplicates for completeness)
DRI
@kballon will act as the DRI for this issue.
Required Resources
- Support Engineers
- SRE
Potential Roadblocks/Things to consider
- This will also notify SEs during shift updates similar to the
@ceocslack handle.
Desired Outcome
What does success look like?
- Support Engineers are able to quickly look up the next on-call engineer via the new
@ceoc-nexthandle.
How do we measure success?
- Support Engineers will participate in trial review correct handle updates.
Where would future feedback go?
- Feedback can be shared in this issue.
Related Issues/MRs/Epics/Tickets
- RFC: Implement @ceoc-next handle for CEOC handover workflow
- feat: update-oncall-usergroups: implement --next-schedules, which selects ingress on-call
Edited by Aysegul Acar