Add escalation step upon no response to tier2 devops (c71ee0e4) · Commits · GitLab.com / Content Sites / handbook

content/handbook/engineering/infrastructure-platforms/incident-management/on-call/tier-2.md

+2 −1

Original line number	Diff line number	Diff line
		@@ -35,7 +35,8 @@ A summary of currently active Tier 2 rotations is listed below. For more detail
		- Coverage: 24x5
		- Schedule: [schedule](https://app.incident.io/gitlab/on-call/schedules/01K611MG8T5CW874Q5JZER3H0Z)
		- Escalation History Link: [escalation](https://app.incident.io/gitlab/on-call/escalations?escalation_path%5Bone_of%5D=01K6P0Q3D6B7AYV0JT41DP0VME)
		- Slack Channel for Rotation Swaps: `#tier-2-devops-rotation-swaps`
		- Slack Channel for Rotation Swaps: [`#tier-2-devops-rotation-swaps`](https://gitlab.enterprise.slack.com/archives/C09LLF79AK0)
		- Escalation upon non-response: `@mention` the EM or SEM/Director for the on-call team member who did not respond, using the slack channel [`#tier-2-devops-rotation-swaps`](https://gitlab.enterprise.slack.com/archives/C09LLF79AK0) to ask for additional support. In the event that leadership does not respond, use `@here + msg` in [`#tier-2-devops-rotation-swaps`](https://gitlab.enterprise.slack.com/archives/C09LLF79AK0) requesting help from another available engineer.

		### Runners Platform