GetQueryOptimizeDataTrend - Database Autonomy Service

Queries query governance trend data.

Operation description

If you use Alibaba Cloud SDK, make sure that the aliyun-sdk-core version is later than V2.1.8. We recommend that you use the latest version.
The version of your Database Autonomy Service (DAS) SDK must be V2.1.8 or later.
If you use an SDK to call operations of DAS, you must set the region ID to cn-shanghai.
This operation supports the following database engines:
- ApsaraDB RDS for MySQL
- PolarDB for MySQL
- ApsaraDB RDS for PostgreSQL

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.

Debug

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:GetQueryOptimizeDataTrend	get	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
Engine	string	Yes	The database engine. Valid values: MySQL PolarDBMySQL PostgreSQL	MySQL
InstanceIds	string	No	The instance IDs. Separate multiple IDs with commas (,).	rm-2ze8g2am97624****
TagNames	string	No	The reserved parameter.	None
Start	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. Note You can specify a start time up to two months earlier than the current time.	1642435200000
End	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, but not later than 00:00:00 (UTC+8) on the current day.	1643040000000
Region	string	No	The region in which the instance resides. Valid values: cn-china: Chinese mainland. cn-hongkong: China (Hong Kong). ap-southeast-1: Singapore. This parameter takes effect only if InstanceIds is left empty. If you leave InstanceIds empty, the system obtains data from the region specified by Region. By default, Region is set to cn-china. If you specify InstanceIds, Region does not take effect and the system obtains data from the region in which the first specified instance resides.** Note If your instances reside in the regions inside the Chinese mainland, set this parameter to cn-china**.	cn-china

Response parameters

Parameter	Type	Description	Example
	object
Code	string	The HTTP status code returned.	200
Message	string	The returned message.	Successful
Data	object	The detailed information.
Total	long	The total number of entries returned.	10
PageNo	integer	The reserved parameter.	None
PageSize	integer	The reserved parameter.	None
Extra	string	The reserved parameter.	None
List	array<object>	The details of the trend data.
QueryOptimizeDataTrends	object
Kpi	string	The name of the metric. Valid values: sqlExecuteCount: the number of executions of slow SQL queries. sqlExecuteCountDiff: the difference in the number of executions of slow SQL queries compared to the previous day. sqlCount: the number of slow SQL templates. sqlCountDiff: the difference in the number of slow SQL templates compared to the previous day. optimizedSqlExecuteCount: the number of optimizable executions of slow SQL queries. optimizedSqlExecuteCountDiff: the difference in the number of optimizable executions of slow SQL queries compared to the previous day. optimizedSqlCount: the number of optimizable slow SQL templates. optimizedSqlCountDiff: the difference in the number of optimizable slow SQL templates compared to the previous day.	sqlExecuteCount
Timestamp	long	The data timestamp. This value is a UNIX timestamp representing the number of milliseconds that have elapsed since January 1, 1970, 00:00:00 UTC.	1643040000000
Value	double	The value of the metric.	1000
RequestId	string	The request ID.	B6D17591-B48B-4D31-9CD6-9B9796B2****
Success	string	Indicates whether the request was successful. Valid values: true false	true

Examples

Sample success responses

JSONformat

{
  "Code": "200",
  "Message": "Successful",
  "Data": {
    "Total": 10,
    "PageNo": 0,
    "PageSize": 0,
    "Extra": "None",
    "List": [
      {
        "Kpi": "sqlExecuteCount",
        "Timestamp": 1643040000000,
        "Value": 1000
      }
    ]
  },
  "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
2023-03-29	The request parameters of the API has changed	View Change Details