Sheriffing/How To/Escalate: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Update BuildDuty to CiDuty. Renaming project)
Line 9: Line 9:
* there's already a status (https://status.mozilla.org/) (but still let MOC know it's tree-impacting)
* 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:
If it's something RelEng can handle (or you also want them to be aware), here's the escalation path:
* ping *|buildduty in #releng
* ping *|ciduty in #ci
* use the !squirrel stalk word in #releng
* use the !squirrel stalk word in #ci
* Follow the escalation route at https://wiki.mozilla.org/ReleaseEngineering#Contacting_Release_Engineering
* Follow the escalation route at https://wiki.mozilla.org/ReleaseEngineering#Contacting_Release_Engineering


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

Revision as of 08:23, 14 May 2018

Guidelines on escalating outages

MOC

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.

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)

Releng and Ciduty

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

TaskCluster