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

Email alerts not sent

GOV.UK sends out emails when certain publications are published. We have set up a check to verify that emails are sent for Drug and medical device alerts and travel advice updates.

https://github.com/alphagov/email-alert-monitoring

If the check fails:

  • Inspect the console logs for the rake task for the job. This will tell you which emails are missing.
  • Check the monitoring inbox to rule out false alerts. Emails are sent to a monitoring inbox at googleapi@digital.cabinet-office.gov.uk. Credentials for the account can be found in the 2nd Line pass store. The test is diacritic-sensitive so you may see false alerts where São Tomé and Principe fails to match Sao Tome and Principe.
  • Search for @tags:"govdelivery" in Kibana.

Resending travel advice emails

If you need to force the sending of a travel advice email alert, there is a rake task in the travel advice publisher, which you can run using this Jenkins job, where the edition ID of the travel advice content item can be found in the URL of the country’s edit page in the travel advice publisher and looks like fedc13e231ccd7d63e1abf65.

More about Icinga alerts

This page is owned by #2ndline and needs to be reviewed