Detecting Anomalies in Large Datasets


Create a job that detects anomalies using asynchronous detection.

You can use asynchronous detection to detect anomalies in both univariate and multivariate detection datasets. Typical use cases suited for asynchronous detecting are:

Detecting anomalies in very large datasets

The maximum number of data points supported by the detectAnomalies REST Synchronous API is 30,000. This might impose restrictions in anomaly detection scenarios in which a large number of data points (typically in the millions) needs to be detected. Using asynchronous detection, you can analyze and detect anomalies in very large datasets upwards of 10 million data points.

Automating detection workflows

In IoT use cases, time-series data is usually collected from a large number of sensors and devices, and it’s stored in a persistent data store such as a database or a file system. Often, this raw data must be preprocessed (enriched) by using PaaS services such as Data Flow before inferencing can be performed. You can easily integrate the asynchronous detection APIs within data processing pipelines, and automate detection workflows.

Postprocessing anomalous events

In certain anomaly detection scenarios, the detection data (detected anomalies) might need to be transformed or enriched before it can be consumed by downstream applications. With asynchronous detection, detected anomalies are saved in an Object Storage bucket. You can use PaaS services such as Data Flow to analyze, process, and enrich the anomalous events. Furthermore, you can consume and render the anomalies in visualization graphs in Oracle Analytics Cloud to enable you to monitor target systems and take corrective actions.

Console
CLI
API

Prerequisites:

You must have a project that contains a trained model for use in an asynchronous Anomaly Detection job.

Open the navigation menu and click Analytics & AI. Under AI Services, click Anomaly Detection.
In the left-side navigation menu, click Projects.
Select the compartment that contains the project that you want to use.
Click the name of the project.

The project details page opens.

Click Jobs.
Click Create job.
(Optional) Enter a unique name (255 character limit) for the resource. If you don't provide a name, one is automatically generated.

For example:

aianomalydetection<resource>20230825155844

(Optional) Enter a description (400 character limit) for the resource.
Select the model that you want to run this job in.
(Optional) Select the amount of sensitivity for the anomaly detection to use from 0 to 1.
Select the input request type that you want to use for the job.
Inline:

Drag a JSON or CSV file into the File box, or use Select file to locate and select it from a local drive.

Object store:

Select the Object Storage bucket that contains the detection data file, and then select the file you that you want to use for this job. Only CSV files are supported.

You can use multiple input buckets and detection data files by clicking Additional input bucket and making further selections.

Select an Object Storage output bucket to store the output files in.

The namespace shows you the tenancy that the job is being created in.

(Optional) Enter a prefix to use to easily identify the results.

For example, if myModel is the prefix, then the result file is myModel/results-file.json.

Click Create job.

The asynchronous job status is initially Accepted until the job starts running; then it's In Progress. When the job finishes the status changes to Succeeded. The time it takes to run the job depends on the size of the detection datasets.

Click the completed asynchronous job to view its details and review the job results.

The anomaly detection results file is saved in a separate folder in the selected Object Storage output bucket. The file name uses the <model-OCID>/<output_bucket_name> naming convention.

<model-OCID> is the OCID of the Anomaly Detection model.

<output_bucket_name> is the Object Storage bucket name.

The anomaly detection results file name is the same as the detection dataset file name suffixed with -results.