Delete Jobs APIedit
Deletes an existing anomaly detection job.
Requestedit
DELETE _xpack/ml/anomaly_detectors/<job_id>
Descriptionedit
All job configuration, model state and results are deleted.
Deleting a job must be done via this API only. Do not delete the
job directly from the .ml-* indices using the Elasticsearch
DELETE Document API. When X-Pack security is enabled, make sure no write
privileges are granted to anyone over the .ml-* indices.
Before you can delete a job, you must delete the datafeeds that are associated
with it. See Delete Datafeeds. Unless the force parameter
is used the job must be closed before it can be deleted.
It is not currently possible to delete multiple jobs using wildcards or a comma separated list.
Path Parametersedit
-
job_id(required) - (string) Identifier for the job
Query Parametersedit
-
force - (boolean) Use to forcefully delete an opened job; this method is quicker than closing and deleting the job.
Authorizationedit
You must have manage_ml, or manage cluster privileges to use this API.
For more information, see Security privileges.
Examplesedit
The following example deletes the total-requests job:
DELETE _xpack/ml/anomaly_detectors/total-requests
When the job is deleted, you receive the following results:
{
"acknowledged": true
}