You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow a ML calendar to apply to all ML jobs defined in the system.
Currently, calendars have lists of jobs and/or groups that the calendar applies to. There are some situations where the calendar should apply to all ML jobs. There is no mechanism for this. It is possible to put all jobs into a default group and attach that to the calendar, but there is an administrator overhead to making sure all new jobs are put in this group.
This adds `_all` to Calendar searches. This enables users to supply the `_all` string in the `job_ids` array when creating a Calendar. That calendar will now be applied to all jobs (existing and newly created).
Closes#45013
benwtrent
added a commit
to benwtrent/elasticsearch
that referenced
this issue
Feb 20, 2020
This adds `_all` to Calendar searches. This enables users to supply the `_all` string in the `job_ids` array when creating a Calendar. That calendar will now be applied to all jobs (existing and newly created).
Closeselastic#45013
This adds `_all` to Calendar searches. This enables users to supply the `_all` string in the `job_ids` array when creating a Calendar. That calendar will now be applied to all jobs (existing and newly created).
Closes#45013
Co-authored-by: Elastic Machine <[email protected]>
Allow a ML calendar to apply to all ML jobs defined in the system.
Currently, calendars have lists of jobs and/or groups that the calendar applies to. There are some situations where the calendar should apply to all ML jobs. There is no mechanism for this. It is possible to put all jobs into a default group and attach that to the calendar, but there is an administrator overhead to making sure all new jobs are put in this group.
Some brief discussion in the forum: https://discuss.elastic.co/t/calendar-events-and-machine-learning-jobs/191678
The text was updated successfully, but these errors were encountered: