Cherry-pick #21994 to 7.x: [Elastic Agent] Fix missing elastic_agent event data #22032
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 #21994 to 7.x branch. Original message:
What does this PR do?
Fixes the events pushed by Elastic Agent monitoring to have the
elastic_agent.*
fields. This also updates the fields fromelastic.agent.id
toelastic_agent.id
to match the datasource that was change toelastic_agent
.Why is it important?
So all events can be coordinated to an Agent.
Checklist
[ ] 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 worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
elastic.agent.*
fields #21864