Get records API

edit

Get records API

edit

Retrieves anomaly records for an anomaly detection job.

Request

edit

GET _ml/anomaly_detectors/<job_id>/results/records

Prerequisites

edit

Requires the monitor_ml cluster privilege. This privilege is included in the machine_learning_user built-in role.

Description

edit

Records contain the detailed analytical results. They describe the anomalous activity that has been identified in the input data based on the detector configuration.

There can be many anomaly records depending on the characteristics and size of the input data. In practice, there are often too many to be able to manually process them. The machine learning features therefore perform a sophisticated aggregation of the anomaly records into buckets.

The number of record results depends on the number of anomalies found in each bucket, which relates to the number of time series being modeled and the number of detectors.

Path parameters

edit

<job_id>: (Required, string) Identifier for the anomaly detection job.

Query parameters

edit

desc: (Optional, Boolean) If true, the results are sorted in descending order.
end: (Optional, string) Returns records with timestamps earlier than this time. Defaults to -1, which means it is unset and results are not limited to specific timestamps.
exclude_interim: (Optional, Boolean) If true, the output excludes interim results. Defaults to false, which means interim results are included.
from: (Optional, integer) Skips the specified number of records. Defaults to 0.
record_score: (Optional, double) Returns records with anomaly scores greater or equal than this value. Defaults to 0.0.
size: (Optional, integer) Specifies the maximum number of records to obtain. Defaults to 100.
sort: (Optional, string) Specifies the sort field for the requested records. By default, the records are sorted by the record_score value.
start: (Optional, string) Returns records with timestamps after this time. Defaults to -1, which means it is unset and results are not limited to specific timestamps.

Request body

edit

You can also specify the query parameters in the request body; the exception are from and size, use page instead:

page

Properties of page

from: (Optional, integer) Skips the specified number of records. Defaults to 0.
size: (Optional, integer) Specifies the maximum number of records to obtain. Defaults to 100.

Response body

edit

The API returns an array of record objects, which have the following properties:

actual: (array) The actual value for the bucket.
bucket_span: (number) The length of the bucket in seconds. This value matches the bucket_span that is specified in the job.
by_field_name: (string) The field used to split the data. In particular, this property is used for analyzing the splits with respect to their own history. It is used for finding unusual values in the context of the split.
by_field_value: (string) The value of the by field.
causes: (array) For population analysis, an over field must be specified in the detector. This property contains an array of anomaly records that are the causes for the anomaly that has been identified for the over field. If no over fields exist, this field is not present. This sub-resource contains the most anomalous records for the over_field_name. For scalability reasons, a maximum of the 10 most significant causes of the anomaly are returned. As part of the core analytical modeling, these low-level anomaly records are aggregated for their parent over field record. The causes resource contains similar elements to the record resource, namely actual, typical, geo_results.actual_point, geo_results.typical_point, *_field_name and *_field_value. Probability and scores are not applicable to causes.
detector_index: (number) A unique identifier for the detector. This identifier is based on the order of the detectors in the analysis_config, starting at zero.
field_name: (string) Certain functions require a field to operate on, for example, sum(). For those functions, this value is the name of the field to be analyzed.
function: (string) The function in which the anomaly occurs, as specified in the detector configuration. For example, max.
function_description: (string) The description of the function in which the anomaly occurs, as specified in the detector configuration.
geo_results.actual_point: (string) The actual value for the bucket formatted as a geo_point. If the detector function is lat_long, this is a comma delimited string of the latitude and longitude.
geo_results.typical_point: (string) The typical value for the bucket formatted as a geo_point. If the detector function is lat_long, this is a comma delimited string of the latitude and longitude.
influencers: (array) If influencers was specified in the detector configuration, this array contains influencers that contributed to or were to blame for an anomaly.
initial_record_score: (number) A normalized score between 0-100, which is based on the probability of the anomalousness of this record. This is the initial value that was calculated at the time the bucket was processed.
is_interim: (Boolean) If true, this is an interim result. In other words, the results are calculated based on partial input data.
job_id: (string) Identifier for the anomaly detection job.
over_field_name: (string) The field used to split the data. In particular, this property is used for analyzing the splits with respect to the history of all splits. It is used for finding unusual values in the population of all splits. For more information, see Performing population analysis.
over_field_value: (string) The value of the over field.
partition_field_name: (string) The field used to segment the analysis. When you use this property, you have completely independent baselines for each value of this field.
partition_field_value: (string) The value of the partition field.
probability: (number) The probability of the individual anomaly occurring, in the range 0 to 1. This value can be held to a high precision of over 300 decimal places, so the record_score is provided as a human-readable and friendly interpretation of this.
multi_bucket_impact: (number) an indication of how strongly an anomaly is multi bucket or single bucket. The value is on a scale of -5.0 to +5.0 where -5.0 means the anomaly is purely single bucket and +5.0 means the anomaly is purely multi bucket.
record_score: (number) A normalized score between 0-100, which is based on the probability of the anomalousness of this record. Unlike initial_record_score, this value will be updated by a re-normalization process as new data is analyzed.
result_type: (string) Internal. This is always set to record.
timestamp: (date) The start time of the bucket for which these results were calculated.
typical: (array) The typical value for the bucket, according to analytical modeling.

Additional record properties are added, depending on the fields being analyzed. For example, if it’s analyzing hostname as a by field, then a field hostname is added to the result document. This information enables you to filter the anomaly results more easily.

Examples

edit

GET _ml/anomaly_detectors/low_request_rate/results/records
{
  "sort": "record_score",
  "desc": true,
  "start": "1454944100000"
}

In this example, the API returns twelve results for the specified time constraints:

{
  "count" : 4,
  "records" : [
    {
      "job_id" : "low_request_rate",
      "result_type" : "record",
      "probability" : 1.3882308899968812E-4,
      "multi_bucket_impact" : -5.0,
      "record_score" : 94.98554565630553,
      "initial_record_score" : 94.98554565630553,
      "bucket_span" : 3600,
      "detector_index" : 0,
      "is_interim" : false,
      "timestamp" : 1577793600000,
      "function" : "low_count",
      "function_description" : "count",
      "typical" : [
        28.254208230188834
      ],
      "actual" : [
        0.0
      ]
    },
  ...
  ]
}

« Get filters API Open anomaly detection jobs API »