Skip to content

Commit

Permalink
[DOCS] Hint for the error "Error extracting container id"
Browse files Browse the repository at this point in the history
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 (#18818), which was restored in 7.7.2 onwards.
- The Kubernetes pod is crashing
  • Loading branch information
lucabelluccini authored May 24, 2021
1 parent 4de534f commit 107904a
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions filebeat/docs/faq.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down

0 comments on commit 107904a

Please sign in to comment.