Queries the notification events of one or more urgency levels within a period.
Operation description
Before you call this operation, take note of the following items:
- If you use Alibaba Cloud SDK or Database Autonomy Service (DAS) SDK to call this operation, we recommend that you use the latest version of the SDK.
- If you use an SDK to call operations of DAS, you must set the region ID to cn-shanghai.
- After your instance is connected to DAS, notification events such as snapshot capture are triggered if DAS detects changes to database monitoring metrics during anomaly detection.
Debugging
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:
- The required resource types are displayed in bold characters.
- 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.
Operation | Access level | Resource type | Condition key | Associated operation |
---|---|---|---|---|
hdm:GetAutonomousNotifyEventsInRange | get | *All Resources * |
| none |
Request parameters
Parameter | Type | Required | Description | Example |
---|---|---|---|---|
__context | string | No | The reserved parameter. | None |
InstanceId | string | No | The instance ID. | rm-18ff4a195d**** |
StartTime | string | Yes | The beginning of the time range to query. Set this parameter to a UNIX timestamp representing the number of milliseconds that have elapsed since January 1, 1970, 00:00:00 UTC. | 1568269711000 |
EndTime | string | Yes | The end of the time range to query. Set this parameter to a UNIX timestamp representing the number of milliseconds that have elapsed since January 1, 1970, 00:00:00 UTC. Note
The end time must be later than the start time.
| 1568265711221 |
NodeId | string | No | The ID of the node in a PolarDB for MySQL cluster. You can call the DescribeDBClusters operation to query the node ID returned by the DBNodeId response parameter. Note
You must specify the node ID if your database instance is a PolarDB for MySQL cluster.
| r-x****-db-0 |
EventContext | string | No | The reserved parameter. | None |
Level | string | No | The urgency level of the events. If you specify this parameter, the MinLevel parameter does not take effect. Valid values:
| Warn |
MinLevel | string | No | The minimum urgency level of the events. Valid values:
| Notice |
PageOffset | string | No | The page number. The value must be a positive integer. Default value: 1. | 1 |
PageSize | string | No | The number of entries per page. | 30 |
Response parameters
Examples
Sample success responses
JSON
format
{
"Code": "200",
"Data": {
"Extra": "None",
"List": {
"T": [
"\"T\": []"
]
},
"PageNo": 1,
"PageSize": 10,
"Total": 4
},
"Message": "Successful",
"RequestId": "B6D17591-B48B-4D31-9CD6-9B9796B2****",
"Success": "true"
}
Error codes
HTTP status code | Error code | Error message |
---|---|---|
400 | InvalidParams | The request parameters are invalid. |
403 | NoPermission | You are not authorized to do this action. |
For a list of error codes, visit the Service error codes.
Change history
Change time | Summary of changes | Operation |
---|