Search cluster logs

post

/20260430/aiDataPlatforms/{aiDataPlatformId}/workspaces/{workspaceKey}/clusters/{clusterKey}/actions/searchLogs

Searches logs within the specified cluster and time range. Supports pagination and filtering.

Request

Path Parameters
Query Parameters
  • Minimum Value: 1
    Maximum Value: 1000
    For list pagination. The maximum number of results per page, or items to return in a paginated "List" call. For important details about how pagination works, see [List Pagination](/iaas/Content/API/Concepts/usingapi.htm#nine).
    Default Value: 100
  • Minimum Length: 1
    For list pagination. The value of the opc-next-page response header from the previous "List" call. For important details about how pagination works, see [List Pagination](/iaas/Content/API/Concepts/usingapi.htm#nine).
Header Parameters
  • For optimistic concurrency control. In the PUT or DELETE call for a resource, set the `if-match` parameter to the value of the etag from a previous GET or POST response for that resource. The resource will be updated or deleted only if the etag you provide matches the resource's current etag value.
  • Unique Oracle-assigned identifier for the request. If you need to contact Oracle about a particular request, please provide the request ID. The only valid characters for request IDs are letters, numbers, underscore, and dash.
  • Minimum Length: 1
    Maximum Length: 64
    A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of running 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 removed from the system, then a retry of the original creation request might be rejected.
Body ()
Request body containing the search parameters for cluster logs.
Root Schema : SearchClusterLogsDetails
Type: object
Request payload for searching logs in a cluster.
Show Source
  • Contains any key and value that you want to search in the logs. Should be provided in the format 'key = value'. As of now supported keys are 'taskRunKey' and 'jobRunKey'
    Example: taskRunKey = c75b2b5e-b104-48ac-ae82-3acbdc638ab2
  • Filters logs based on the event type. Supported only when `logContentTypeContains` is `events`.
    Example: CREATING
  • The execution context identifier associated with the log. Supported only when `logContentTypeContains` is `executor` or `driver`.
  • The string represent the type of compute logs Common values include `events`, `driver`, `executor`.
    Example: events
  • The severity level of the log messages to filter. Common values include `INFO`, `WARN`, `ERROR`, `DEBUG`, etc. Supported only when `logContentTypeContains` is `executor` or `driver`.
    Example: ERROR
  • Filters logs based on the output stream type. - This includes standard output (`stdout`) for regular program output - and standard error (`stderr`) for error messages and diagnostics. Only supported when logContentTypeContains=executor/driver.
    Example: stderr
  • The string represent a filter to search message string from the log Supported only when `logContentTypeContains` is `events`.
  • The unique request identifier used for tracking the API call. Supported only when `logContentTypeContains` is `executor` or `driver`.
    Example: bce8d78b-6f12-4a99-95d2-3f44440c54a9
  • The string represent the specific of compute nodes Common values include `spark-driver`, `spark-executor-1`.
    Example: executor-1
  • The thread identifier that generated the log. Supported only when `logContentTypeContains` is `executor` or `driver`.
  • Start filter log's date and time, in RFC 3339 format.
  • End filter log's date and time, in RFC 3339 format.
Back to Top

Response

Supported Media Types

200 Response

Successful operation. A collection of logs for the specified parameters is retrieved.
Headers
  • For pagination of a list of items. When paging through a list, if this header appears in the response, then a partial list might have been returned. Include this value as the `page` parameter for the subsequent GET request to get the next batch of items.
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : ClusterLogCollection
Type: object
Results of a cluster log list.
Show Source
Nested Schema : items
Type: array
List of cluster logs.
Show Source
Nested Schema : ClusterLogsSummary
Type: object
Response payload containing search results and metadata.
Show Source
Nested Schema : fields
Type: array
List of log field schema information.
Show Source
Nested Schema : results
Type: array
List of search results.
Show Source
Nested Schema : SearchResultSummary
Type: object
Summary of the search response.
Show Source
Nested Schema : FieldInfo
Type: object
Schema details of log fields.
Show Source
Nested Schema : SearchResult
Type: object
A single search result.
Show Source
Nested Schema : data
Type: object
The actual log data with field mappings.

400 Response

Bad Request (invalid query parameters, malformed headers, and so on).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

401 Response

Unauthorized (missing or expired credentials, and so on).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

404 Response

Not Found. The requested resource was not found.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

409 Response

Conflict. Request conflicts with the current state of the resource.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

412 Response

Precondition Failed (One or more conditions in request failed).
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

429 Response

Too Many Requests. Too many requests sent to the server in a short period.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

500 Response

Internal Server Error. The server encountered an unexpected condition preventing fulfilment of the request.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source

Default Response

Unknown Error. Error is not recognized by the system.
Headers
  • Unique Oracle-assigned ID for the request. If you need to contact Oracle about a particular request, please provide the request ID.
Body ()
Root Schema : Error
Type: object
Error information.
Show Source
Back to Top