From 64785c793c49a71fc5f852b1a3b935dbfde5c370 Mon Sep 17 00:00:00 2001 From: Richard Towers Date: Fri, 21 Jun 2024 18:57:10 +0100 Subject: [PATCH] Remove redundant docs on alerts for search reranking There's no longer an alert for this. I'm reasonably confident we're also not using the machine learning it refers to. There are no sagemaker endpoints in our AWS account. --- ...search-reranker-healthcheck-not-ok.html.md | 29 ------------------- 1 file changed, 29 deletions(-) delete mode 100644 source/manual/alerts/search-reranker-healthcheck-not-ok.html.md diff --git a/source/manual/alerts/search-reranker-healthcheck-not-ok.html.md b/source/manual/alerts/search-reranker-healthcheck-not-ok.html.md deleted file mode 100644 index f39ade20cd2..00000000000 --- a/source/manual/alerts/search-reranker-healthcheck-not-ok.html.md +++ /dev/null @@ -1,29 +0,0 @@ ---- -owner_slack: "#govuk-2ndline-tech" -title: Search reranker healthcheck not ok -parent: "/manual.html" -layout: manual_layout -section: Icinga alerts ---- - -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][aws-sagemaker]. - -### How do I investigate this? - -Find out why the Search API can't connect to SageMaker. - -- 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][sagemaker-endpoint] - -[aws-sagemaker]: https://aws.amazon.com/sagemaker/ -[sagemaker-endpoint]: https://eu-west-1.console.aws.amazon.com/sagemaker/home?region=eu-west-1#/endpoints/govuk-production-search-ltr-endpoint