Flag to enable the service to return estimates for all data points rather than just the anomalous data points
The OCID of the compartment that starts the job.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
Detect anomaly job description.
Detect anomaly job display name.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
Id of the job.
The current state of the batch document job.
The current state details of the batch document job.
The OCID of the trained model.
The OCID of the project.
The value that customer can adjust to control the sensitivity of anomaly detection Note: Numbers greater than Number.MAX_SAFE_INTEGER will result in rounding issues.
Usage of system tag keys. These predefined keys are scoped to namespaces. Example: {@code { "orcl-cloud": { "free-tier-retained": "true" } }}
Job accepted time
Job finished time
Job started time
Anomaly Job contains information for asynchronous detection of anomalies.