Options
All
  • Public
  • Public/Protected
  • All
Menu

Interface CreateDetectAnomalyJobRequest

example

Click here to see how to use CreateDetectAnomalyJobRequest.

Hierarchy

Properties

Properties

createDetectAnomalyJobDetails

createDetectAnomalyJobDetails: CreateDetectAnomalyJobDetails

The input is either:

  • JSON object in the request. This object is defined, and the SDK generates the object for it.
  • Data embedded as Base64 string in format of either:
    • CSV
    • JSON If this option is used, then you must provide the content of specified CSV or JSON in Base64 encoded string. The Embedded JSON has to be in the same format as the inline request JSON.

Optional opcRequestId

opcRequestId: undefined | string

The client request ID for tracing.

Optional opcRetryToken

opcRetryToken: undefined | string

A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations. For example, if a resource has been deleted and purged from the system, then a retry of the original creation request might be rejected.

Optional retryConfiguration

retryConfiguration: RetryConfiguration

RetryConfiguration to be used for the request NOTE : Retries are not supported for requests that have binary or stream bodies this also affects UploadManager operations For all requests with binary/stream bodies, retry attempts are not made