StopTimingSyntheticTask - Application Real-Time Monitoring Service

Stops scheduled synthetic monitoring tasks.

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:
- 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
arms:StopTimingSyntheticTask	update	SyntheticTask acs:arms:{#regionId}:{#accountId}:synthetictask/{#TaskId}	none	none

Request parameters

Parameter	Type	Required	Description	Example
RegionId	string	No	The region ID.	cn-hangzhou
TaskIds	array	Yes	The task IDs.
	string	Yes	The task ID.	3cee3d23ev4342342csc

Response parameters

Parameter	Type	Description	Example
	object
RequestId	string	The request ID.	1A9C645C-C83F-4C9D-8CCB-29BEC9E1****
Code	long	The HTTP status code. The status code 200 indicates that the request was successful. Other status codes indicate that the request failed.	200
Message	string	The returned message.	success
Data	boolean	Indicates whether the request was successful. Valid values: true and false.	true

Examples

Sample success responses

JSONformat

{
  "RequestId": "1A9C645C-C83F-4C9D-8CCB-29BEC9E1****",
  "Code": 200,
  "Message": "success",
  "Data": true
}

Error codes

HTTP status code	Error code	Error message
400	ParameterMissing	%s
400	ParameterIllegal	%s
400	TaskQuotaLimit	%s
400	ParameterRegionIllegal	%s
400	DuplicateTagKey	Param tagKey is duplicate.
400	TagNumOUT	the number of tag is out .
400	NoPermissionUSER	user no permission
403	RAMNotAuthorize	%s
403	STSNotAuthorize	%s
403	IllegalUserAccess	%s
403	APINotAuthorize	%s
403	CommercialStatusException	%s
403	SyntheticTrailExpired	%s
403	SyntheticInDebt	%s
403	SyntheticDailyTimesExhausted	%s
403	SyntheticDailyLimit	%s
403	INNER_PROHIBIT

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

Change history

Change time	Summary of changes	Operation
2023-12-06	The Error code has changed	View Change Details