Cherry-pick #16866 to 7.x: Improve some logging messages for add_kubernetes_metadata processor #16893
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.
Cherry-pick of PR #16866 to 7.x branch. Original message:
What does this PR do?
Switch from Debug to Error when unrecoveral events happen and add extra debug messages when indexing and matching pods.
I was trying to debug why my configs wouldn't work and I was forced to enable debug to notice that the
add_kubernetes_metadata
processor was failing because my configs were wrong.Sadly, my configs weren't working even after I fixed the above and it was a bit painful to figure out what was going on because there weren't enough debug messages to understand what index keys, matches, and metadata was being processed by filebeat.
Why is it important?
It makes operations and debugging easier
Checklist