From 99ff11f07ba7f4d05df365ba27aa86db7e3e7f57 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Edu=20Gonz=C3=A1lez=20de=20la=20Herr=C3=A1n?= <25320357+eedugon@users.noreply.github.com> Date: Mon, 4 Nov 2024 09:50:50 +0100 Subject: [PATCH] Update docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc Co-authored-by: Andrew Gizas --- .../ingest-management/troubleshooting/troubleshooting.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc b/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc index 0367881d0..65c01fd62 100644 --- a/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc +++ b/docs/en/ingest-management/troubleshooting/troubleshooting.asciidoc @@ -919,7 +919,7 @@ In an already installed system, the API Key is stored in a `Secret` named `elast + These metrics (`state_*`) are retrieved by one of the Pods acting as `leader` (as described in <>), so in order to troubleshoot that situation: + -. Determine which Pod owns the leadership `lease` in the cluster, with: +. Determine which Pod owns the [leadership](https://www.elastic.co/guide/en/fleet/current/kubernetes_leaderelection-provider.html#:~:text=Provides%20the%20option%20to%20enable,Elastic%20Agent%20holds%20the%20leadership.) `lease` in the cluster, with: + [source,sh] ----