All Products
Search
Document Center

AnalyticDB:DescribeApsActionLogs

Last Updated:Mar 10, 2025

Queries the logs of a real-time data ingestion job for an AnalyticDB for MySQL cluster.

Operation description

  • General endpoint: adb.aliyuncs.com.
  • Regional public endpoint: adb.<region-id>.aliyuncs.com. Example: adb.cn-hangzhou.aliyuncs.com.
  • Regional Virtual Private Cloud (VPC) endpoint: adb-vpc.<region-id>.aliyuncs.com. Example: adb-vpc.cn-hangzhou.aliyuncs.com.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
adb:DescribeApsActionLogsnone
*DBClusterLakeVersion
acs:adb:{#regionId}:{#accountId}:dbcluster/{#DBClusterId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
DBClusterIdstringYes

The ID of the AnalyticDB for MySQL Data Lakehouse Edition cluster.

Note You can call the DescribeDBClusters operation to query the IDs of all AnalyticDB for MySQL clusters within a region.
amv-bp1r053byu48p****
RegionIdstringYes

The region ID of the cluster.

Note You can call the DescribeRegions operation to query the most recent region list.
cn-hangzhou
StartTimestringYes

The start time of the logs to be queried. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mmZ format. The time must be in UTC.

2023-02-11T08:30:00Z
EndTimestringYes

The end time of the logs to be queried. Specify the time in the ISO 8601 standard in the yyyy-MM-ddTHH:mmZ format. The time must be in UTC.

Note The end time must be later than the start time. The maximum time range that can be specified is 30 days.
2023-02-11T09:30:00Z
WorkloadIdstringYes

The ID of the real-time data ingestion job.

aps-hz109vpvt4fg8528d****
KeywordstringNo

The keyword that you want to use for fuzzy match in the query.

table_test
StagestringNo

The phase during which the logs to be queried were generated. Valid values:

  • StructureMigrate: schema migration.
  • FullDataSync: full data synchronization.
  • IncrementalSync: incremental data synchronization.
Note If you do not specify this parameter, logs of all the phases are queried.
FullDataSync
StatestringNo

The types of the logs. Separate multiple log types with commas (,). Valid values:

  • INFO
  • WARN
  • ERROR
Note If you do not specify this parameter, logs of all types are queried.
INFO,WARN,ERROR
PageSizeintegerNo

The number of entries per page. Valid values:

  • 30 (default)
  • 50
  • 100
30
PageNumberintegerNo

The page number. Pages start from page 1. Default value: 1.

1

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

A5EDBA27-AF3E-5966-9503-FD1557E19167
DBClusterIdstring

The ID of the AnalyticDB for MySQL Data Lakehouse Edition (V3.0) cluster.

amv-bp1r053byu48p****
WorkloadIdstring

The ID of the real-time data ingestion job.

aps-hz109vpvt4fg8528d****
TotalCountstring

The total number of entries returned.

3
PageSizestring

The number of entries per page.

30
PageNumberstring

The page number.

1
ActionLogsarray<object>

The queried logs.

SlowLogRecordobject
Timestring

The time when the log was generated. The time follows the ISO 8601 standard in the yyyy-MM-ddTHH:mm:ssZ format. The time is displayed in UTC.

2023-02-01T05:46:30Z
Stagestring

The phase during which the log was generated. Valid values:

  • StructureMigrate: schema migration.
  • FullDataSync: full data synchronization.
  • IncrementalSync: incremental data synchronization.
FullDataSync
Statestring

The type of the log. Multiple log types are separated by commas (,). Valid values:

  • INFO
  • WARN
  • ERROR
INFO,WARN,ERROR
Contextstring

The content of the log.

DDL migration job finished
AccessDeniedDetailstring

The information about the request denial.

{ "AuthAction": "xxx", "AuthPrincipalDisplayName": "sampleName", "AuthPrincipalOwnerId": "111111111111111111", "AuthPrincipalType": "SubUser", "AuthResource": "xxx", "NoPermissionType": "xxx", "PolicyType": "xxx" }

Examples

Sample success responses

JSONformat

{
  "RequestId": "A5EDBA27-AF3E-5966-9503-FD1557E19167",
  "DBClusterId": "amv-bp1r053byu48p****",
  "WorkloadId": "aps-hz109vpvt4fg8528d****",
  "TotalCount": "3",
  "PageSize": "30",
  "PageNumber": "1",
  "ActionLogs": [
    {
      "Time": "2023-02-01T05:46:30Z",
      "Stage": "FullDataSync",
      "State": "INFO,WARN,ERROR",
      "Context": "DDL migration job finished"
    }
  ],
  "AccessDeniedDetail": "{\n  \"AuthAction\": \"xxx\",\n  \"AuthPrincipalDisplayName\": \"sampleName\",\n  \"AuthPrincipalOwnerId\": \"111111111111111111\",\n  \"AuthPrincipalType\": \"SubUser\",\n  \"AuthResource\": \"xxx\",\n  \"NoPermissionType\": \"xxx\",\n  \"PolicyType\": \"xxx\"\n}"
}

Error codes

HTTP status codeError codeError messageDescription
404InvalidDBCluster.NotFoundThe DBClusterId provided does not exist in our records.The specified DBClusterId parameter does not exist. Make sure that the DBClusterId value is valid.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2024-05-14The Error code has changed. The response structure of the API has changedView Change Details
2024-01-24The Error code has changedView Change Details
2023-06-21The Error code has changed. The request parameters of the API has changedView Change Details
2023-03-30The Error code has changedView Change Details