From 107904a49373e63c8726fe74904d0d009d0f7409 Mon Sep 17 00:00:00 2001 From: Luca Belluccini Date: Mon, 24 May 2021 10:36:17 +0100 Subject: [PATCH] [DOCS] Hint for the error "Error extracting container id" When using the Kubernetes add metadata processor, the error `Error extracting container id - source value does not contain matcher's logs_path` might be reported in some cases. Typical issues: - The `logs_path` is incorrect - We had some problems in the past (7.7.0) due to a change in behavior (https://github.com/elastic/beats/pull/18818), which was restored in 7.7.2 onwards. - The Kubernetes pod is crashing --- filebeat/docs/faq.asciidoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/filebeat/docs/faq.asciidoc b/filebeat/docs/faq.asciidoc index 4547e165fb99..ddcdb6a8898f 100644 --- a/filebeat/docs/faq.asciidoc +++ b/filebeat/docs/faq.asciidoc @@ -5,6 +5,13 @@ This section describes common problems you might encounter with {beatname_uc}. Also check out the https://discuss.elastic.co/c/beats/{beatname_lc}[{beatname_uc} discussion forum]. +[[filebeat-kubernetes-metadata-error-extracting-container-id]] +=== Error extracting container id while using Kubernetes metadata + +The `add_kubernetes_metadata` processor might throw the error `Error extracting container id - source value does not contain matcher's logs_path`. +There might be some issues with the matchers definitions or the location of `logs_path`. +Please verify the Kubernetes pod is healthy. + [[filebeat-network-volumes]] === Can't read log files from network volumes