Delete a model snapshot Generally available; Added in 5.4.0

DELETE /_ml/anomaly_detectors/{job_id}/model_snapshots/{snapshot_id}
Api key auth Basic auth Bearer auth

You cannot delete the active model snapshot. To delete that snapshot, first revert to a different one. To identify the active model snapshot, refer to the model_snapshot_id in the results from the get jobs API.

Required authorization

  • Cluster privileges: manage_ml

Path parameters

  • job_id string Required

    Identifier for the anomaly detection job.

  • snapshot_id string Required

    Identifier for the model snapshot.

Responses

  • 200 application/json
    Hide response attribute Show response attribute object
    • acknowledged boolean Required

      For a successful response, this value is always true. On failure, an exception is returned instead.
DELETE /_ml/anomaly_detectors/{job_id}/model_snapshots/{snapshot_id} 
DELETE _ml/anomaly_detectors/farequote/model_snapshots/1491948163 
resp = client.ml.delete_model_snapshot( job_id="farequote", snapshot_id="1491948163", )
const response = await client.ml.deleteModelSnapshot({ job_id: "farequote", snapshot_id: 1491948163, });
response = client.ml.delete_model_snapshot( job_id: "farequote", snapshot_id: "1491948163" )
$resp = $client->ml()->deleteModelSnapshot([ "job_id" => "farequote", "snapshot_id" => "1491948163", ]);
curl -X DELETE -H "Authorization: ApiKey $ELASTIC_API_KEY" "$ELASTICSEARCH_URL/_ml/anomaly_detectors/farequote/model_snapshots/1491948163"
client.ml().deleteModelSnapshot(d -> d .jobId("farequote") .snapshotId("1491948163") );
Response examples (200)
A successful response when deleting an existing model snapshot. 
{ "acknowledged": true }