Cherry-pick #24380 to 7.x: Use alias to report container image in k8s parts #24471
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 #24380 to 7.x branch. Original message:
What does this PR do?
This PR leverages
type :alias
forkubernetes.container.image
so as to copy the fields under ECScontainer.image.name
.This affects metadata collected by kubernetes autodiscover provider,
add_kubernetes_metadata
processor andstate_container
metricset.Why is it important?
In order to have a persistent way to report ECS container fields, without the need to duplicate fields and store both which will impact ECS.
How to test this PR locally
fields.yml
on your testing env is properly updated with thealias
change and manuallysetup
and verify that mappings are properly loaded in ES.Make sure that
container.image.name
exist in the final documents in ES and you able to search on based on it whilekubernetes.container.image
is not populated in the event but is searchable because of thealias
.3. Check that
add_kubernetes_metadata
processor works:Make sure that
container.image.name
exist in the final documents in ES and you able to search on based on it whilekubernetes.container.image
is not populated in the event but is searchable because of thealias
.state_container
metricset enabled that,container.image.name
exist in the final documents in ES and you able to search based on it whilekubernetes.container.image
is not populated in the event but is searchable because of thealias
.Related issues
Screenshots