Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Ability to lookup / track action type executor responses #63755

Closed
mikecote opened this issue Apr 16, 2020 · 4 comments
Closed

Ability to lookup / track action type executor responses #63755

mikecote opened this issue Apr 16, 2020 · 4 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework insight Issues related to user insight into platform operations and resilience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

The request is to be able to track the response an action executor returns after being invoked. A similar response to the /_execute API would work and should track responses when invoked from alerts.
@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Apr 16, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

@mikecote
Copy link
Contributor Author

This could either be done via event log or something else.

@pmuellr
Copy link
Member

pmuellr commented Apr 22, 2020

Event Log seems like the logical place for this. I only worry about size, and finding a property to store it in. This would end up being a non-indexed field, not searchable, only available via the _source.

One possibility to cut down on the size would be to only store "error" responses, since that's likely all a customer would be interested in. We could make that a kibana config option, perhaps.

@mikecote
Copy link
Contributor Author

Another note from #62668 (comment)

as soon as we add action/alert executor input/results/etc to the event log, we'll have to revisit.

@mikecote mikecote mentioned this issue Apr 28, 2020
Closed
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added Feature:Actions/Framework Issues related to the Actions Framework insight Issues related to user insight into platform operations and resilience Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework and removed Feature:Alerting labels Aug 13, 2021
@gmmorris gmmorris added the estimate:needs-research Estimated as too large and requires research to break down into workable issues label Aug 18, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/Framework Issues related to the Actions Framework Feature:Alerting/RuleActions Issues related to the Actions attached to Rules on the Alerting Framework insight Issues related to user insight into platform operations and resilience Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@pmuellr @gmmorris @kobelb @mikecote @elasticmachine @YulNaumenko