Delete anomaly jobs from a calendar Generally available; Added in 6.2.0

DELETE /_ml/calendars/{calendar_id}/jobs/{job_id}
Api key auth Basic auth Bearer auth

Required authorization

  • Cluster privileges: manage_ml

Path parameters

  • calendar_id string Required

    A string that uniquely identifies a calendar.

  • job_id string | array[string] Required

    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.

Responses

  • 200 application/json
    Hide response attributes Show response attributes object
DELETE /_ml/calendars/{calendar_id}/jobs/{job_id} 
DELETE _ml/calendars/planned-outages/jobs/total-requests 
resp = client.ml.delete_calendar_job( calendar_id="planned-outages", job_id="total-requests", )
const response = await client.ml.deleteCalendarJob({ calendar_id: "planned-outages", job_id: "total-requests", });
response = client.ml.delete_calendar_job( calendar_id: "planned-outages", job_id: "total-requests" )
$resp = $client->ml()->deleteCalendarJob([ "calendar_id" => "planned-outages", "job_id" => "total-requests", ]);
curl -X DELETE -H "Authorization: ApiKey $ELASTIC_API_KEY" "$ELASTICSEARCH_URL/_ml/calendars/planned-outages/jobs/total-requests"
Response examples (200)
A successful response when deleting an anomaly detection job from a calendar. 
{ "calendar_id": "planned-outages", "job_ids": [] }