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

Search API app healthcheck not ok

See also: how healthcheck alerts work on GOV.UK

Elasticsearch connectivity is not OK

The Search API uses elasticsearch as an underlying data store and search engine.

If the application cannot connect to the elasticsearch cluster, this will prevent end users performing searches.

Note: We use a managed elasticsearch, Amazon Elasticsearch Service, rather than running our own.

To solve this issue, look at the logs of the application to see what is wrong.

How do I investigate this?

Find out why the Search API can’t connect to elasticsearch.

Reranker is not OK

The Search API uses machine learning to rank search results based on analytics data. If this alert fires, something has gone wrong with that process and we’re serving results as they were ordered by elasticsearch.

Unlike the other healthcheck failures, this does not mean that Search API is serving errors. Only that it is serving potentially worse results.

The machine learning model is hosted in Amazon SageMaker.

How do I investigate this?

Find out why the Search API can’t connect to elasticsearch.

  • Look at the error message in the healthcheck response
  • Look at the Search API logs
  • Check the status of the SageMaker endpoint in the AWS console
This page was last reviewed on 11 September 2020. It needs to be reviewed again on 11 March 2021 by the page owner #govuk-2ndline .
This page was set to be reviewed before 11 March 2021 by the page owner #govuk-2ndline. This might mean the content is out of date.