Skip to main content
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

Icinga alerts

Email Alert API: Unprocessed content changes

This means that there are some emails informing users of content changes which haven’t been processed within the time we would expect. This may be fine and the emails will eventually go out, but it’s worth some investigation.

  • warning - content_changes unprocessed for over 5 minutes
  • critical - content_changes unprocessed for over 10 minutes

See the ProcessContentChangeWorker for more information.

Some useful queries and Rake tasks:

Check which content changes are affected

ContentChange.where("created_at < ?", 10.minutes.ago).where(processed_at: nil)

Check number of subscription contents built for a content change (you would expect this number to keep going up)

SubscriptionContent.where(content_change: content_change).count

Resend the emails for a content change (ignore ones that have already gone out)

ProcessContentChangeWorker.new.perform(content_change.id)

Resend the emails for a content change in bulk (ignore ones that have already gone out)

ContentChange.where("created_at < ?", 10.minutes.ago).where(processed_at: nil).map { |content_change| ProcessContentChangeWorker.new.perform(content_change.id)  }

Check sent, pending and failed email counts for a content change

 $ bundle exec rake report:content_change_email_status_count[<content_change_id>]

Check failed email ids and failure reasons for a content change

 $ bundle exec rake report:content_change_failed_emails[<content_change_id>]
This page was last reviewed on 8 January 2020. It needs to be reviewed again on 8 July 2020 by the page owner #govuk-2ndline .
This page was set to be reviewed before 8 July 2020 by the page owner #govuk-2ndline. This might mean the content is out of date.