IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Delete anomaly detection jobs from calendar API
editDelete anomaly detection jobs from calendar API
editDeletes anomaly detection jobs from a calendar.
Request
editDELETE _ml/calendars/<calendar_id>/jobs/<job_id>
Prerequisites
editRequires the manage_ml
cluster privilege. This privilege is included in the
machine_learning_admin
built-in role.
Path parameters
edit-
<calendar_id>
- (Required, string) A string that uniquely identifies a calendar.
-
<job_id>
- (Required, string) An identifier for the anomaly detection jobs. It can be a job identifier, a group name, or a comma-separated list of jobs or groups.
Examples
editresp = client.ml.delete_calendar_job( calendar_id="planned-outages", job_id="total-requests", ) print(resp)
response = client.ml.delete_calendar_job( calendar_id: 'planned-outages', job_id: 'total-requests' ) puts response
const response = await client.ml.deleteCalendarJob({ calendar_id: "planned-outages", job_id: "total-requests", }); console.log(response);
DELETE _ml/calendars/planned-outages/jobs/total-requests
When the job is removed from the calendar, you receive the following results:
{ "calendar_id": "planned-outages", "job_ids": [] }