Cherry-pick #22189 to 7.x: Kubernetes metadata enhancements #22536
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 #22189 to 7.x branch. Original message:
What does this PR do?
kubernetes.host.hostname
on node metadata,add_resource_metadata
required to enabled) for both events coming from autodiscovered pods but also for events enriched byadd_kubernetes_metadata
add_resource_metadata
required to enabled) for both events coming from autodiscovered pods but also for events enriched byadd_kubernetes_metadata
add_resource_metadata
section for autodiscover and add_kubernetes_metadata.Why is it important?
This information is useful in various ways. See more on the respective issue: #20434
How to test this PR manually
Test with autodiscover provider
kubernetes.node.hostname
field is populated.Test with add_kubernetes_metadata processor
kubernetes.node.hostname
field is populated as well askubernetes.node.*
andkubernetes.namespace.*
.Related issues
kubernetes.node.hostname
field with the actual hostname of the node #20434Screenshots
Filebeat & add_kubernetes_metadata:
Autodiscover: