FetchLosslessRuleList - Microservices Engine - Alibaba Cloud Documentation Center

Retrieves the rules for graceful start and shutdown.

Operation description

You can call the FetchLosslessRuleList operation to retrieve the configuration rules for graceful start and shutdown.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

The table below describes the authorization required to call this API. You can define it in a Resource Access Management (RAM) policy. The table's columns are detailed below:

Action: The actions can be used in the Action element of RAM permission policy statements to grant permissions to perform the operation.
API: The API that you can call to perform the action.
Access level: The predefined level of access granted for each API. Valid values: create, list, get, update, and delete.
Resource type: The type of the resource that supports authorization to perform the action. It indicates if the action supports resource-level permission. The specified resource must be compatible with the action. Otherwise, the policy will be ineffective.
- For APIs with resource-level permissions, required resource types are marked with an asterisk (*). Specify the corresponding Alibaba Cloud Resource Name (ARN) in the Resource element of the policy.
- For APIs without resource-level permissions, it is shown as All Resources. Use an asterisk (*) in the Resource element of the policy.
Condition key: The condition keys defined by the service. The key allows for granular control, applying to either actions alone or actions associated with specific resources. In addition to service-specific condition keys, Alibaba Cloud provides a set of common condition keys applicable across all RAM-supported services.
Dependent action: The dependent actions required to run the action. To complete the action, the RAM user or the RAM role must have the permissions to perform all dependent actions.

Action

Access level

Resource type

Condition key

Dependent action

mse:FetchLosslessRuleList

get

*All Resource

*

None

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	Yes	The region ID.	cn-beijing
AppName	string	No	The application name.	spring-boot-sample
Namespace	string	No	The namespace.	default
AppId	string	No	The application ID.	hyaziyb6sc@86827c61f5ed8fc
PageNumber	integer	Yes	The page number.	1
PageSize	integer	Yes	The number of entries to return on each page.	10
AcceptLanguage	string	No	The language of the response. Valid values: zh: Chinese. en: English.	zh-CN

Response elements

Parameter	Type	Description	Example
	object	The return value.
RequestId	string	The request ID.	56D9E600-6348-4260-B35F-583413F****
Success	boolean	Indicates whether the request was successful. Valid values: `true`: The request was successful. `false`: The request failed.	True
Code	integer	The response code.	200
ErrorCode	string	The error code.	Success
HttpStatusCode	integer	The HTTP status code.	200
Message	string	The message.	success
Data	object	The response data.
PageNumber	integer	The page number.	1
PageSize	integer	The number of entries returned per page.	10
TotalSize	integer	The total number of entries.	36
Results	array	The response data.
	object	The response data.
AppName	string	The application name.	echo-demo
AppId	string	The application ID.	hkhon1po62@24810bf4364aea1
Count	integer	The total number of instances.	3
Enable	boolean	Indicates whether graceful start is enabled. Valid values: `true`: enabled. `false`: disabled.	true
WarmupTime	integer	The prefetching duration. Unit: seconds.	60
DelayTime	integer	The registration latency. Unit: seconds.	60
FuncType	integer	The slope of the prefetching curve.	2
Aligned	boolean	Indicates whether service registration is complete before readiness probe.	true
Related	boolean	Indicates whether service prefetching is complete before readiness probe.	false
LossLessDetail	boolean	Specifies whether to display online and offline processing details.	false
Notice	boolean	Indicates whether notification is enabled.	true

Examples

Success response

JSON format

{
  "RequestId": "56D9E600-6348-4260-B35F-583413F****",
  "Success": true,
  "Code": 200,
  "ErrorCode": "Success",
  "HttpStatusCode": 200,
  "Message": "success",
  "Data": {
    "PageNumber": 1,
    "PageSize": 10,
    "TotalSize": 36,
    "Results": [
      {
        "AppName": "echo-demo",
        "AppId": "hkhon1po62@24810bf4364aea1",
        "Count": 3,
        "Enable": true,
        "WarmupTime": 60,
        "DelayTime": 60,
        "FuncType": 2,
        "Aligned": true,
        "Related": false,
        "LossLessDetail": false,
        "Notice": true
      }
    ]
  }
}

Error codes

HTTP status code	Error code	Error message	Description
400	InvalidParameter	Parameter error:%s	Request parameter error: %s
400	IllegalRequest	Invalid request:%s	Invalid request: %s
500	InternalError	Console error. Try again later:%s	Console error. Try again later: %s
403	NoPermission	You are not authorized to perform this operation:%s	You do not have the permission to use this interface:%s
404	NotFound	Not found:%s	The resource does not exist:%s

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.