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

Nginx 429 too many requests

Nginx is configured with a rate limit in the cache servers to stop unusual load from being redirected to the rest of the systems. Sometimes a robot or a malicious client could hit the cache servers above the rate limit, in which case Nginx will reject requests, log an error message in the error log file and generate an HTTP 429 response code.

The alert should link to a Graphite graph. If you determine this is a spike, it is best to check the Nginx logs in Kibana to determine why Nginx is rejecting requests (for instance, too many requests coming from a single IP, or the same page being requested at a high rate).

This page was last reviewed on 10 March 2020. It needs to be reviewed again on 10 September 2020 by the page owner #govuk-2ndline .

This page was set to be reviewed before 10 September 2020 by the page owner #govuk-2ndline. This might mean the content is out of date.