Send data to an anomaly detection job for analysis Deprecated Generally available; Added in 5.4.0

POST /_ml/anomaly_detectors/{job_id}/_data

IMPORTANT: For each job, data can be accepted from only a single connection at a time. It is not currently possible to post data to multiple jobs using wildcards or a comma-separated list.

Required authorization

  • Cluster privileges: manage_ml

Path parameters

  • job_id string Required

    Identifier for the anomaly detection job. The job must have a state of open to receive and process the data.

Query parameters

  • reset_end string | number

    Specifies the end of the bucket resetting range.

  • reset_start string | number

    Specifies the start of the bucket resetting range.

application/json

Body Required

object object

Responses

  • 200 application/json
    Hide response attributes Show response attributes object
    • job_id string Required
    • processed_record_count number Required
    • processed_field_count number Required
    • input_bytes number Required
    • input_field_count number Required
    • invalid_date_count number Required
    • missing_field_count number Required
    • out_of_order_timestamp_count number Required
    • empty_bucket_count number Required
    • sparse_bucket_count number Required
    • bucket_count number Required
    • earliest_record_timestamp number

      Time unit for milliseconds

    • latest_record_timestamp number

      Time unit for milliseconds

    • last_data_time number

      Time unit for milliseconds

    • latest_empty_bucket_timestamp number

      Time unit for milliseconds

    • latest_sparse_bucket_timestamp number

      Time unit for milliseconds

    • input_record_count number Required
    • log_time number

      Time unit for milliseconds

POST /_ml/anomaly_detectors/{job_id}/_data
curl \
 --request POST 'http://api.example.com/_ml/anomaly_detectors/{job_id}/_data' \
 --header "Authorization: $API_KEY" \
 --header "Content-Type: application/json" \
 --data '[{}]'