All Products
Search
Document Center

Application Real-Time Monitoring Service:StopTimingSyntheticTask

Last Updated:May 17, 2024

Stops scheduled synthetic monitoring tasks.

Debugging

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

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.
OperationAccess levelResource typeCondition keyAssociated operation
arms:StopTimingSyntheticTaskWrite
  • SyntheticTask
    acs:arms:{#regionId}:{#accountId}:synthetictask/{#TaskId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
RegionIdstringNo

The region ID.

cn-hangzhou
TaskIdsarrayYes

The task IDs.

stringYes

The task ID.

3cee3d23ev4342342csc

Response parameters

ParameterTypeDescriptionExample
object
RequestIdstring

The request ID.

1A9C645C-C83F-4C9D-8CCB-29BEC9E1****
Codelong

The HTTP status code. The status code 200 indicates that the request was successful. Other status codes indicate that the request failed.

200
Messagestring

The returned message.

success
Databoolean

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 codeError codeError message
400ParameterMissing%s
400ParameterIllegal%s
400TaskQuotaLimit%s
400ParameterRegionIllegal%s
400DuplicateTagKeyParam tagKey is duplicate.
400TagNumOUTthe number of tag is out .
400NoPermissionUSERuser no permission
403RAMNotAuthorize%s
403STSNotAuthorize%s
403IllegalUserAccess%s
403APINotAuthorize%s
403CommercialStatusException%s
403SyntheticTrailExpired%s
403SyntheticInDebt%s
403SyntheticDailyTimesExhausted%s
403SyntheticDailyLimit%s
403INNER_PROHIBIT

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

Change history

Change timeSummary of changesOperation
2023-12-06The Error code has changedsee changesets
Change itemChange content
Error CodesThe Error code has changed.
    Error Codes 403 change
    delete Error Codes: 400