[DOCS] Hint for the error "Error extracting container id" #25824
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
botelastic
bot
added
the
needs_team
|
Pinging @elastic/obs-docs (Team:Docs) |
botelastic
bot
removed
the
needs_team
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪❕ Flaky test reportNo test was executed to be analysed. |
bmorelli25
approved these changes
May 24, 2021
There was a problem hiding this comment.
Thank you, @lucabelluccini! Would you like me to take care of the backports for this PR?
|
Hi! We're labeling this issue as |
This was referenced Jun 29, 2021
bmorelli25
pushed a commit
to bmorelli25/beats
that referenced
this pull request
Jun 29, 2021
bmorelli25
pushed a commit
to bmorelli25/beats
that referenced
this pull request
Jun 29, 2021
bmorelli25
added a commit
that referenced
this pull request
Jun 29, 2021
…6584) Co-authored-by: Luca Belluccini <[email protected]>
bmorelli25
added a commit
that referenced
this pull request
Jun 29, 2021
…6585) Co-authored-by: Luca Belluccini <[email protected]>
mdelapenya
added a commit
to mdelapenya/beats
that referenced
this pull request
Jun 30, 2021
* master: (25 commits) fix: Force PLATFORMS environment variable when we build Elastic Agent dependencies on arm64 (elastic#26415) macos for metricbeat to run in the extended meta-stage (elastic#26573) Packaging: add arm7 platform in the main pipeline (elastic#26575) [Heartbeat] Skip flakey timer queue test (elastic#26592) Update to "read_pipeline" permission (elastic#26465) (elastic#26580) API keys do not reflect the need for read_pipeline (elastic#26466) (elastic#26582) Add Fleet agent.id to Agent monitoring data (elastic#26548) Add kinesis metricset (elastic#25989) Refactor of system/memory metricset (elastic#26334) Introduce httpcommon package in libbeat (add support for Proxy) (elastic#25219) [Filebeat] change multiline configuration in awss3 input to parsers (elastic#25873) docs: Hint for the error "Error extracting container id" (elastic#25824) [Docs] Fixed metricbeat redis exported field CPU descriptions (elastic#25846) (elastic#26496) Update urllib to 1.26.5. (elastic#26380) Update golang.org/x/crypto (elastic#26448) [Filebeat] Update Fortinet Ingest Pipeline (elastic#24816) Move parsers outside of filestream input so others can use them as well (elastic#26541) [Filebeat] Fix `threatintel.indicator.url.full` field not populating (elastic#26508) [Filebeat] Add network direction processor to Zeek and Suricata modules (elastic#24620) Logging code cleanup related to Nomad auto-discovery (elastic#26498) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
When using the Kubernetes add metadata processor, the error
Error extracting container id - source value does not contain matcher's logs_pathmight be reported in some cases.Typical issues:
logs_pathis incorrectWhy is it important?
It can provide a possible explanation of a common issue
Checklist
Maintainer's Checklist