The content type of the log data.
Discovery data type
A value of {@code 100-continue} requests preliminary verification of the request method, path, and headers before the request body is sent. If no error results from such verification, the server will send a 100 (Continue) interim response to indicate readiness for the request body. The only allowed value for this parameter is "100-Continue" (case-insensitive).
The log group OCID that gets mapped to the logs in the discovery data.
The Logging Analytics namespace used for the request.
Metadata key and value pairs separated by a semicolon. Example k1:v1;k2:v2;k3:v3
The client request ID for tracing.
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.
Identifies the type of request payload.
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
Discovery data
Click here to see how to use UploadDiscoveryDataRequest.