Delete an anomaly detection job
/_ml/anomaly_detectors/{job_id} All job configuration, model state and results are deleted. It is not currently possible to delete multiple jobs using wildcards or a comma separated list. If you delete a job that has a datafeed, the request first tries to delete the datafeed. This behavior is equivalent to calling the delete datafeed API with the same timeout and force parameters as the delete job request.
Required authorization
- Cluster privileges:
manage_ml
Parameters
path Path Parameters
| Name | Type |
|---|---|
job_id
required
Identifier for the anomaly detection job. | type TypesId = string |
query Query Parameters
| Name | Type |
|---|---|
force Use to forcefully delete an opened job; this method is quicker than closing and deleting the job. | boolean |
delete_user_annotations Specifies whether annotations that have been added by the user should be deleted along with any auto-generated annotations when the job is reset. | boolean |
wait_for_completion Specifies whether the request should return immediately or wait until the job deletion completes. | boolean |
Responses
acknowledged: boolean;
}