Latest revision as of 13:38, 7 July 2019

Guidelines on escalating outages

Escalate infrastructure / issues with the continuous integration (CI) in #ci on IRC. Request list of best suited contacts from Aryx.

Other signs of a global issue include:

you see nagios alerts for the issue in #sysadmins
there's already a status (https://status.mozilla.org/) (but still let MOC know it's tree-impacting)

If it's something RelEng can handle (or you also want them to be aware), here's the escalation path:

ping in #taskcluster (see https://wiki.mozilla.org/TaskCluster for coverage in any timezone)

@@ Line 2: / Line 2: @@
 = Guidelines on escalating outages =
-== MOC ==
+== RelOps ==
-If you cannot pinpoint the affected system or team responsible, going directly to the MOC can save a lot of time, especially during off-hours. The MOC can be reached in irc #moc. The MOC knows how to contact and escalate any issue.
+Escalate infrastructure / issues with the continuous integration (CI) in #ci on IRC. Request list of best suited contacts from Aryx.
 Other signs of a global issue include:
@@ Line 9: / Line 9: @@
 * there's already a status (https://status.mozilla.org/) (but still let MOC know it's tree-impacting)
-== Releng ==
+== Releng and Ciduty ==
 If it's something RelEng can handle (or you also want them to be aware), here's the escalation path:
-* ping *|buildduty in #releng
-* use the !squirrel stalk word in #releng
 * Follow the escalation route at https://wiki.mozilla.org/ReleaseEngineering#Contacting_Release_Engineering
 == TaskCluster ==
 * ping in #taskcluster (see https://wiki.mozilla.org/TaskCluster for coverage in any timezone)