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.

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

[Task Manager] Introduce generic scheduling field in place of interval #51472

Closed
gmmorris opened this issue Nov 22, 2019 · 2 comments
Closed
Assignees
Labels
Feature:Alerting Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.6.0

Comments

@gmmorris
Copy link
Contributor

gmmorris commented Nov 22, 2019

We want to change Tasks such that they can handle a variety of different kinds of scheduling, with interval being the single implementation we currently provide.

We'll address this by doing the following:

  1. The interval field will be marked as deprecated on TaskManager, but we'll continue to support it until 8.0.0
  2. Along side interval we'll introduce a field called sked (up for discussion ;)) which can take any shaped object, and migrate all existing intervals into the shape: { interval: "10m" }. This will allow us to support future shapes such as { cron: "0 0 0 0 0" } or { "hourly" : { "minute" : 30 } } similar to watcher.
  3. We will make this change in both TaskManager and Alerting (two separate PRs) for 7.6, to keep both APIs aligned, but Alerting will continue to rely on it's own internal implementation as moving to TM probably can't be done in time for 7.6.
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-stack-services (Team:Stack Services)

@gmmorris gmmorris moved this from To-Do 7.6 to In Progress in Make it Action Dec 11, 2019
@bmcconaghy bmcconaghy added Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) and removed Team:Stack Services labels Dec 12, 2019
@gmmorris gmmorris moved this from In Progress to Done (Ordered by most recent) in Make it Action Dec 17, 2019
@gmmorris
Copy link
Contributor Author

closed by #52727

@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
Labels
Feature:Alerting Feature:Task Manager Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.6.0
Projects
No open projects
Make it Action
  
Done (Ordered by most recent)
Development

No branches or pull requests

5 participants