Resets and upgrades the log analysis feature. You can call this operation only when the log analysis feature uses the pay-as-you-go billing method.
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 Resourcesis 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 |
|---|---|---|---|---|
| yundun-sas:ResetLogShipper | update | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| Ttl | integer | No | The global log retention period. Note
This parameter is supported only when the log analysis feature uses the pay-as-you-go billing method.
| 180 |
| HotTtl | integer | No | The global retention period of hot data. Note
The value of this parameter must be at least 7 and smaller than the log retention period. Unit: days.
| 7 |
| LogMetaList | array<object> | No | The settings of the log analysis feature. | |
| object | No | The setting of the log analysis feature. | ||
| ConfigLogStore | string | No | The Logstore that you want to configure. Note
You can call the DescribeLogMeta operation to query the Logstore.
| sas-security-log |
| Status | string | No | The status of the log analysis feature. Valid values:
| enabled |
| Ttl | integer | No | The log retention period of the Logstore. Note
If you specify this parameter for the Logstore, the global log retention period specified by the Ttl parameter is overwritten.
| 60 |
| HotTtl | integer | No | The retention period of hot data in the Logstore. Note
The value of this parameter must be at least 7 and smaller than the log retention period. Unit: days. If you specify this parameter for the Logstore, the global retention period of hot data specified by the HotTtl parameter is overwritten.
| 7 |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "D2E31293-DAAC-574B-B816-A18EA0A6****"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | IllegalHotTTL | The hot storage TTL is invalid. | The hot storage data must be stored for at least 7 days and must be less than the data storage time. |
| 403 | NoPermission | caller has no permission | You are not authorized to do this operation. |
| 500 | ServerError | ServerError | - |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|