Cherry-pick #16003 to 7.x: Reduce global logging in some docker/k8s + AD related packages #16083
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 #16003 to 7.x branch. Original message:
What does this PR do?
Reduce/Remove usage of global logging functions in docker and kubernetes related processors and Autodiscovery providers.
The change adds the structured logging field
libbeat.processor: <name>
to theadd_kubernetes_metadata
andadd_docker_metadata
processors. Structured logging is transitive. Error/debug logs produced by thelibbeat/common/docker
, andlibbeat/common/kubernetes
packages will also mention the processor name.Why is it important?
Remove usage of global logging functions and improved structured logging support.
Checklist
- [ ] I have commented my code, particularly in hard-to-understand areas- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksAuthor's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs