@@ -41,6 +41,16 @@ filling in the name of the person you swapped with. Also see [this article](http
- You can view the [schedule](https://gitlab.pagerduty.com/schedules#PIQ317K) and the [escalation policy](https://gitlab.pagerduty.com/escalation_policies#PKV6GCH) on PagerDuty.
- After each shift, _if_ there was an alert / incident, the on call person will send a hand off email to the next on call explaining what happened and what's ongoing, pointing at the right issues with the progress.
## GitHost Emergency On-Call Rotation
- We do 7 days of 12 hour shifts, based on your location.
- After 10 minutes, if the alert has not been acknowledged, _everyone_ on the GitHost on-call rotation is alerted.
- You can view the [schedule](https://gitlab.pagerduty.com/schedules#PHCLLKL) and the [escalation policy](https://gitlab.pagerduty.com/escalation_policies#PV6RZLT) on PagerDuty.
### Triggering a GitHost Emergency page
- In Slack, anyone can type `/githost-emergency` to trigger a GitHost Emergency. When paging an on-call Product Support Engineer, please make sure to specify what ticket this page is in reference to. This is vital information that should go along with every page.
- Use this only if a GitHost customer instance is down.
