Table of contents
This page describes what to do in case of an Icinga alert. For more information you could search the govuk-puppet repo for the source of the alert

PagerDuty drill

Every week we test PagerDuty to make sure it can phone to alert us to any issues.

Cron creates a file on disk. Icinga raises a critical alert when that file exists with an Icinga contact group set so that PagerDuty is notified. After a short amount of time, cron will remove the file to resolve the alert. The code that does this is in Puppet.

Note: The drill runs within the AWS environment while we migrate our apps to AWS. If you need to trigger the drill manually, make sure you’re logged in to the AWS monitoring instance.

You don’t need to take any action for this alert. The primary in-office 2nd line should escalate the call to the secondary who should escalate it to “escalations” to ensure that phone redirection is working. The person on “escalations” will resolve the PagerDuty alert to prevent anyone else being phoned.

This page was last reviewed on 9 January 2019. It needs to be reviewed again on 9 July 2019 by the page owner #govuk-2ndline .
This page was set to be reviewed before 9 July 2019 by the page owner #govuk-2ndline. This might mean the content is out of date.