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

[Task Manager] Ephemeral tasks follow up #106139

Closed
chrisronline opened this issue Jul 19, 2021 · 2 comments
Closed

[Task Manager] Ephemeral tasks follow up #106139

chrisronline opened this issue Jul 19, 2021 · 2 comments
Labels
estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Task Manager R&D Research and development ticket (not meant to produce code, but to make a decision) Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@chrisronline
Copy link
Contributor

chrisronline commented Jul 19, 2021 •
edited
Loading

In #97311, we introduced (are introducing) an alternative method to executing actions that result from rule detection. This functionality will be opt-in by default and require users to understand this feature and explicitly enable it. We don't expect many users to use it right away and need to perform some follow up tasks before considering this feature opt-out by default.

  • We want some way to distinguish ephemeral tasks from non ephemeral tasks in the event log (and presumably in general too)
  • We need to figure out how to integrate this feature into functional tests without needing to create duplicate test suites
  • Increase documentation (perhaps a blog posts) to explain this feature and why users might want to use it
  • Add support for docker configs (from this comment: [Alerting] Change execution of alerts from async to sync #97311 (review))

(This list is a WIP and might change over time)
@chrisronline chrisronline added Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jul 19, 2021
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote added this to Backlog in Kibana Alerting Jul 21, 2021
@gmmorris gmmorris added loe:needs-research This issue requires some research before it can be worked on or estimated R&D Research and development ticket (not meant to produce code, but to make a decision) labels Aug 11, 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
@XavierM XavierM removed this from Backlog in Kibana Alerting Jan 6, 2022
@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
@mikecote
Copy link
Contributor

Closing as we decided to move away from supporting ephemeral tasks: #151463.

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:Task Manager R&D Research and development ticket (not meant to produce code, but to make a decision) Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
AppEx: ResponseOps - Execution & Connectors
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
5 participants
@chrisronline @gmmorris @kobelb @mikecote @elasticmachine