PutMonitorGroupDynamicRule - CloudMonitor - Alibaba Cloud Documentation Center

Creates or modifies an alert rule to dynamically add instances that meet the rule to an application group.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer.

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
cms:PutMonitorGroupDynamicRule	create	MonitorGroup acs:cms::{#accountId}:group/{#groupId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
GroupId	long	Yes	The ID of the application group.	123456
GroupRules	array<object>	Yes	None.
	object	Yes	None.
FilterRelation	string	Yes	The logical operator used between conditional expressions in the alert rule. Valid values of N: 1 to 3. Valid values: and: The instances that meet all the conditional expressions are automatically added to the application group. or: The instances that meet one of the conditional expressions are automatically added to the application group.	and
Filters	array<object>	Yes	None.
	object	No	None.
Value	string	Yes	The value to be matched with the specified field. Valid values of N: 1 to 3.	nginx
Name	string	Yes	The name of the field based on which instances are filtered. Valid values of N: 1 to 3. Only hostnames are supported. Example: hostName.	hostName
Function	string	Yes	The method that is used to filter instances. Valid values of N: 1 to 3. Valid values: contains: contains notContains: does not contain startWith: starts with a prefix endWith: ends with a suffix	contains
Category	string	Yes	The cloud service to which the alert rule is applied. Valid values of N: 1 to 3. Valid values: ecs: Elastic Compute Service (ECS) rds: ApsaraDB RDS slb: Server Load Balancer (SLB)	ecs
IsAsync	boolean	No	The mode for creating the alert rule. Valid values: true: creates asynchronously false (default): creates synchronously	false

For more information about common request parameters, see Common parameters.

Response parameters

Parameter	Type	Description	Example
	object
Code	integer	The status code. Note The status code 200 indicates that the request was successful.	200
Message	string	The error message.	The specified resource is not found.
RequestId	string	The request ID.	3E73F1AB-D195-438A-BCA7-2F4355789C58
Success	boolean	Indicates whether the request was successful. Valid values: true false	true

Examples

Sample success responses

JSONformat

{
  "Code": 200,
  "Message": "The specified resource is not found.",
  "RequestId": "3E73F1AB-D195-438A-BCA7-2F4355789C58",
  "Success": true
}

Error codes

HTTP status code	Error code	Error message	Description
206	%s	%s	-
400	ParameterInvalid	%s	-
401	AccessDeniedException	You donot have sufficient access to perform this action.	-
402	LimitExceeded	The quota for this customer had been reached.	-
403	AccessForbidden	%s	-
404	ResourceNotFound	The specified resource is not found.	The specified resource is not found.
412	OverLimit	Matched instances count was over limit	-
429	Throttli∂ngException	The request was denied due to request throttling.	-
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

No change history