Modifies configurations of the lossless online and offline feature.
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 |
|---|---|---|---|---|
| mse:ModifyLosslessRule | get | *All Resources * |
| none |
Request parameters
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| RegionId | string | Yes | The ID of the region. | cn-beijing |
| AppName | string | No | The name of the application. | wx-work-api |
| Namespace | string | No | The microservice namespace to which the rule applies. | default |
| AppId | string | Yes | The ID of the application. | c644n5frmc@3e75f25fd4***** |
| Enable | boolean | Yes | Specifies whether to enable the alert rule. Valid values:
| false |
| WarmupTime | long | Yes | The prefetching duration. | 60 |
| DelayTime | long | Yes | The registration latency. | 1 |
| FuncType | long | Yes | The slope of the prefetching curve. | 1 |
| Aligned | boolean | Yes | Specifies whether to align the lifecycle of the application in the Kubernetes cluster with that of the microservice. | true |
| Related | boolean | Yes | Specifies whether to associate with service prefetching. | true |
| LossLessDetail | boolean | No | Specifies whether to display online and offline processing details. | false |
| Notice | boolean | No | Specifies whether to enable notification. | false |
| AcceptLanguage | string | No | The language of the response. Valid values:
| zh |
Response parameters
Examples
Sample success responses
JSONformat
{
"RequestId": "3369AD10-F1A6-4E6F-B99E-20F51826****",
"Success": true,
"Code": 200,
"ErrorCode": "mse-100-000",
"HttpStatusCode": 200,
"Message": "modifyLosslessRule success",
"Data": "null"
}Error codes
| HTTP status code | Error code | Error message | Description |
|---|---|---|---|
| 400 | duplicatedClusterAliasName | duplicated cluster alias name | The instance name is duplicate. User another name. |
| 400 | illegalRequest | illegal request:%s | Invalid request: %s |
| 403 | NoPermission | You are not authorized to perform this operation:%s | You do not have the permission to use this interface:%s |
| 404 | clusterNotFound | cluster not found | The cluster is not found. |
| 500 | systemError | system error | An error occurred on the system. Try again later. |
For a list of error codes, visit the Service error codes.
Change history
| Change time | Summary of changes | Operation |
|---|---|---|
| 2023-04-11 | The Error code has changed. The request parameters of the API has changed. The response structure of the API has changed | View Change Details |