Cherry-pick #16987 to 7.x: Fix issue where autodiscover hints default configuration was not being copied. #17002
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 #16987 to 7.x branch. Original message:
What does this PR do?
FIxes issue where when a default configuration is provided to autodiscovery in filebeat it would cause the elasticsearch module to have log messages repeated and appear in different datasets.
Why is it important?
Without this change log messages would be repeated and reported in different datasets unless
hints.default_config.enabled: false
was set. Which also prevented filebeat from reading the logs of pods that didn't have the annotation ofco.elastic.logs/enabled: true
.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksHow to test this PR locally
cd filebeat && PACKAGES="linux/amd64" mage package
event.dataset
.Related issues
Use cases
Screenshots
Logs