-
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
Advance scheduling (cron syntax, etc). #50272
Comments
Pinging @elastic/kibana-stack-services (Team:Stack Services) |
I'm just gonna put this here: https://crontab.guru/ almost two decades of working with Cron and I still find it to be one of the worst formats I've ever had to work with. 🤣 |
It would be interesting to see how much customers use |
Discussing this with the @elastic/kibana-stack-services team, we've decided to make an api change in Alerting & Task Manager to allow us to take a generic In a later release we'll add support for cron like scheduling along side |
@gmmorris ++ can we create a new issue to change the mapping structure of interval within alerting / task manager for 7.6? You can add it to the 7.6 alerting bucket. Similar to what we discussed, we'll put the capability in place for it by simply changing how we store the value in alerts / task manager. |
No prob ;) |
It would be nice to be able to add blackout periods too. Sometimes it’s easier to say when an alert shouldn’t fire, than when it should. |
Users need the ability to schedule alerts at a specific time every day, at their local time and automatically adjusting to DST changes. |
Moving from |
From: #132265 (closed in favour of this issue).
|
Any progress on this matter? |
cc @shanisagiv1. We can probably re-use rrule that is used for maintenance windows and snoozing for this. |
Recently ran into a use case where this would have been helpful. Need to run a rule once every 24 hours within a given time window. Had to do some manual effort to disable/enable the rule around the window to get the rule's execution to "sync" to it. |
Still need this +1 |
|
+1, this feature would be very helpful |
Is there an update on this? |
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 acron
one, and we can later add things likehourly
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 ofinterval
orcron
, which should be fairly future-proof, as we can add more properties likehourly
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).
The text was updated successfully, but these errors were encountered: