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

High memory for application

This alert triggers when the application process uses too much memory.

For more info, you can also read the page for the alert that triggers when a machine is out of memory.

If you’re having trouble with Mapit, see the Mapit specific page

Fix memory leaks

A common cause of the alerts are memory leaks. For Rails applications you can try diagnosing the error with the derailed gem.

Restart the application

If you can’t find the source of the memory leak you can restart the application.

Increase the alerting threshold

Sometimes the alerting thresholds are too low. You can change them in hieradata_aws/common.yaml hieradata/common.yaml

govuk::apps::the_warning::nagios_memory_warning: 2500
govuk::apps::the_warning::nagios_memory_critical: 2500

An example of upping the threshholds can be found here

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