-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cherry-pick #17894 to 7.x: Agent push ECS meta to fleet #17921
Conversation
[Elastic-Agent] Agent push ECS meta to fleet (elastic#17894)
Pinging @elastic/ingest-management (Project:fleet) |
@michalpristas as @ruflin noted in the sync this will indeed be a problem we need to send an object to Kibana. I have updated the issues in elastic/kibana#64173 to mention its an object. I believe we have a method in common package that can exploded the keys into multiples nested object.. I haven't found it. |
@michalpristas Can you sync with @nchaulet so we have the appropriate change at the same time? |
@nchaulet ping me when you have a PR ready i will do the change overnight and test it with your branch. we can merge at the same day so snapshots are ok |
…lastic#18006) * use meta object * changelog * agent.* => elastic.agent.*
💚 Build SucceededExpand to view the summary
Build stats
|
Cherry-pick of PR #17894 to 7.x branch. Original message:
What does this PR do?
This PR enhances local metadata sent to fleet on checkin and enroll to conform to ecs format.
It still keeps 3 items it was sending before which will be removed when kibana confirms it does not need it.
Why is it important?
Fixes: #14461
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.