Review CEOC, CMOC, and emergency booster to reduce redundant info
CEOC, CMOC, and emergency booster training modules has a lot of overlap.
- In Customer Emergency On-Call there’s a very detailed stage on familiarizing with Pagerduty and setting it up. In GitLab-com CMOC it’s a single bullet to request access. Perhaps there should be a separate module on PagerDuty explicitly that both link to.
- Both have the exact same ‘Read Incident Management’ page with following bullets.
- Both have the CMOC training recording
- Stage 3 of Customer Emergency On Call goes into monitoring of Gitlab.com and some of the pieces, but not as in depth as the Gitlab-com list.
- There seems to be some tasks that should be overlapped between the two, such as expectations for being on call, that aren’t. I would propose merging these two trainings, beginning with shared portions (status.io, pagerduty, on call expectations, etc) and then branching what is specific to each form of on call. Not certain if there’s an easy way to do that via MR.
- the Gitlab-com emergency booster training: the Sentry bits are linked/spelled out a bit better than the other modules.