opened 02:37AM - 12 Nov 19 UTC
Feature:Alerting
Feature:Task Manager
R&D
Team:ResponseOps
Feature:Alerting/RulesFramework
estimate:needs-research
For reference, Watcher allows some uber-flexible ways of scheduling, documented …as "triggers", documented here:
https://www.elastic.co/guide/en/elasticsearch/reference/current/trigger-schedule.html
I think I'd be happy with having our existing `interval` type scheduling and a `cron` one, and we can later add things like `hourly` if cron ends up being too obtuse for humans (it will).
So, I think what should happen is we create a top-level `schedule` object that takes one of `interval` or `cron`, which should be fairly future-proof, as we can add more properties like `hourly` later.
Note, this probably then also applies to Task Manager, as we attempt to move alerting's scheduling directly to task manager (seems like they are kinda independent right now).