DescribeParametersHistory - ApsaraDB for OceanBase - Alibaba Cloud Documentation Center

You can call this operation to query the modification history of cluster or tenant parameters.

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:
- 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.

Operation	Access level	Resource type	Condition key	Associated operation
oceanbase:DescribeParametersHistory	get	All Resources ``	none	none

Request parameters

Parameter	Type	Required	Description	Example
InstanceId	string	Yes	The ID of the OceanBase cluster.	ob317v4uif****
Dimension	string	Yes	The type of the parameter. Valid values: CLUSTER and TENANT.	TENANT
DimensionValue	string	No	The resource ID of the parameter type. You can leave this parameter unspecified when you call this operation to query cluster parameters. In the case of tenant parameters, pass the tenant ID.	t4qx8****
StartTime	string	Yes	The start time of querying the slow query execution. The value must be UTC time in the format of YYYY-MM-DDThh:mm:ssZ.	2021-06-13 15:40:43
EndTime	string	Yes	The end time of the time range for querying the SQL execution history. The value must be UTC time in the format of YYYY-MM-DDThh:mm:ssZ.	2021-09-13 15:40:43
PageSize	integer	Yes	The number of rows to return on each page. Maximum value: 100. Default value: 10	10
PageNumber	integer	Yes	The number of the page to return. Start value: 1 Default value: 1	1

Response parameters

Parameter	Type	Description	Example
	object	The return result of the request.
RequestId	string	The ID of the request.	EE205C00-30E4-XXXX-XXXX-87E3A8A2AA0C
Respond	object	The list of parameter modification records.
TotalCount	integer	The total count, which takes effect in a pagination query.	5
PageNumber	integer	The number of the page to return. Start value: 1 Default value: 1	1
Parameters	array<object>	The information about parameters.
Parameters	object	The information about parameters.
Status	string	The modification status of the parameter. Valid values: APPLIED: The parameter was modified. SCHEDULING: The parameter was to be modified.	APPLIED
OldValue	string	The value of the parameter before the modification.	10
UpdateTime	string	The time when the parameter modification took effect.	2024-11-26T08:03:34Z
CreateTime	string	The time when the parameter modification was initiated.	2024-11-26T08:03:34Z
DimensionValue	string	The resource ID of the parameter type. When you called this operation to query the modification history of cluster parameters, the value is DEFAULT_DIMENSION_VALUE. When you called this operation to query the modification history of tenant parameters, the value is the tenant ID.	t69uo********
Name	string	The name of the parameter.	connect_timeout
NewValue	string	The value of the parameter after the modification.	30

Examples

Sample success responses

JSONformat

{
  "RequestId": "EE205C00-30E4-XXXX-XXXX-87E3A8A2AA0C",
  "Respond": {
    "TotalCount": 5,
    "PageNumber": 1,
    "Parameters": [
      {
        "Status": "APPLIED",
        "OldValue": 10,
        "UpdateTime": "2024-11-26T08:03:34Z",
        "CreateTime": "2024-11-26T08:03:34Z",
        "DimensionValue": "t69uo********",
        "Name": "connect_timeout",
        "NewValue": 30
      }
    ]
  }
}

Error codes

HTTP status code	Error code	Error message
500	InternalError	The request processing has failed due to some unknown error.

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

Change history

Change time	Summary of changes	Operation
2024-10-29	The Error code has changed. The response structure of the API has changed	View Change Details