Force buffered data to be processed
Deprecated /_ml/anomaly_detectors/{job_id}/_flush The flush jobs API is only applicable when sending data for analysis using the post data API. Depending on the content of the buffer, then it might additionally calculate new results. Both flush and close operations are similar, however the flush is more efficient if you are expecting to send more data for analysis. When flushing, the job remains open and is available to continue analyzing data. A close operation additionally prunes and persists the model state to disk and the job must be opened again before analyzing further data.
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 |
|---|---|
advance_time Specifies to advance to a particular time value. Results are generated and the model is updated for data from the specified time interval. | type TypesDateTime = type TypesEpochTimeUnitMillis = TypesUnitMillis | string |
calc_interim If true, calculates the interim results for the most recent bucket or all buckets within the latency period. | boolean |
end When used in conjunction with | type TypesDateTime = type TypesEpochTimeUnitMillis = TypesUnitMillis | string |
skip_time Specifies to skip to a particular time value. Results are not generated and the model is not updated for data from the specified time interval. | type TypesDateTime = type TypesEpochTimeUnitMillis = TypesUnitMillis | string |
start When used in conjunction with | type TypesDateTime = type TypesEpochTimeUnitMillis = TypesUnitMillis | string |
Request Body
advance_time?:
calc_interim?: boolean;
end?:
skip_time?:
start?:
}