-
Notifications
You must be signed in to change notification settings - Fork 82
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
Propagate checkin status to agent record #420
Conversation
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪 |
I wouldn't backport unless we were backporting the new UX as well. Not sure we are buying ourselves much otherwise. |
@scunningham We already have code in Fleet that looks at |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@scunningham based on the discussion from @jen-huang and the comment from @jfsiii I would backport this to 7.13.x too. If it's fine with you I will just add the label. |
@ph I have no objection. |
What does this PR do?
Writes out the checkin status field to the last_checkin_status field in the agent record. This is necessary to support UX changes.
Why is it important?
UX needs it.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Setup local fleet server and point an agent at it. You can validate field change using the dev tools in kibana.
Screenshots