-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
EMT-248: implement ack resource to accept event payload to acknowledge agent actions #60218
EMT-248: implement ack resource to accept event payload to acknowledge agent actions #60218
Conversation
@elasticmachine merge upstream |
const body: PostAgentAcksResponse = { | ||
action: 'acks', | ||
success: true, | ||
items: [...agentActions], |
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.
Do we want to return the updated actions?
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.
I think it's not going to be used by agent so we can remove it
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.
Ok, so a simple ack is fine. Also noticed it was a ton of data so it makes sense.
Pinging @elastic/ingest-management (Feature:Fleet) |
…kie/kibana into EMT-248_implement_action_acks
This is changing the contract with agents cc @michalpristas @ph |
@michalpristas @ph I think we could restrict type and subtype of events send during acknowledgement, what are the possible values you are going to send? |
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.
LGTM 🚀 maybe we can add more restriction and allow only ACTION_RESULT
as event type for now
💚 Build SucceededHistory
To update your PR or re-run it, just comment with: |
* master: (30 commits) [TSVB] fix text color when using custom background color (elastic#60261) Fix import to timefilter from in TSVB (elastic#60296) [NP] Get rid of usage redirectWhenMissing service (elastic#59777) [SIEM] Fix Timeline footer styling (elastic#59587) [ML] Fixes to error handling for analytics jobs and file data viz (elastic#60249) Give better stack traces for Unhandled Promise Rejection warnings (elastic#60235) resolves elastic#58905 (elastic#60120) Added variables button for text fields in Pagerduty component. (elastic#60189) adds test that action vars are rendered for alert action parms (elastic#60310) Closes 59786 by removing the update toast (elastic#60172) [EPM] Packages list tabs (elastic#60167) Added message variables button for Webhook body form field (elastic#60174) Revert "adds new test (elastic#60064)" [Maps] move MapSavedObject type out of telemetry (elastic#60127) [Reporting] Fix error handling for job handler in route (elastic#60161) [Endpoint] TEST: verify alerts page header says 'Alerts' (elastic#60206) EMT-248: implement ack resource to accept event payload to acknowledge agent actions (elastic#60218) Migrate dual validated range (elastic#59689) Embeddable triggers (elastic#58440) [Endpoint] Sample data generator CLI script (elastic#59952) ...
Summary
https://github.com/elastic/endpoint-app-team/issues/248
This change implements the acknowledgment api for agent actions. It provides a richer payload for agent to respond to actions using the event schema. The request from the agents are stored as event saved objects.
Change Notes:
Now expect AgentEvent as body
All events and all actions must belong to the currently authorized agent.
Checklist