Before you start on 2nd line
Before you start your shift you’ll need access to the accounts we use and our communication channels.
The 2nd line dashboard can be viewed here.
We use Icinga to monitor our platform and alert us when things go wrong. Please ensure you can access (if remote you will need to be on the VPN):
Zendesk is our support ticketing system. Request an account if you don’t have one yet - Signon access is required so speak to your fellow 2nd Liners if you haven’t got this. This diagram shows you how to process tickets.
This is our escalation workflow for some key alerts that are likely to require urgent attention. When an alert that triggers pager duty goes off we require one of the 2nd line to acknowledge them, otherwise they will be escalated further. The sort of issues which would generate pagerduty are for key aspects of the site becoming unavailable or a large quantity of error pages served.
Please check you can sign in to PagerDuty. Speak to the delivery manager if you cannot sign in.
There is a PagerDuty drill every Wednesday morning at 11am. You will be called by PagerDuty and must escalate the incident to the person on 3rd line. When you receive this call do not acknowledge it, instead escalate it so that each person in the workflow can be alerted.
You can also find out what to do if there’s an incident.
Follow these Slack channels while you’re working on 2nd line:
- #govuk-2ndline - the main channel for people on 2nd line
- #govuk-deploy - every time a Staging/Production deploy is done, this is automatically posted to - people also manually post when putting branches on Integration for testing
- #govuk-developers - this is a general channel for developers and can be a good place to ask questions if you are struggling