Modifies a site monitoring task.

This topic provides an example to show how to change the name of a site monitoring task whose ID is 2c8dbdf9-a3ab-46a1-85a4-f094965e**** to HanZhou_ECS1. The response shows that the task name is changed.

Debugging

OpenAPI Explorer automatically calculates the signature value. For your convenience, we recommend that you call this operation in OpenAPI Explorer. OpenAPI Explorer dynamically generates the sample code of the operation for different SDKs.

Request parameters

Parameter Type Required Example Description
Action String Yes ModifySiteMonitor

The operation that you want to perform. Set the value to ModifySiteMonitor.

TaskId String Yes 2c8dbdf9-a3ab-46a1-85a4-f094965e****

The ID of the site monitoring task.

Address String No http://www.aliyun.com

The URL or IP address that is monitored by the task.

TaskName String No HanZhou_ECS1

The name of the site monitoring task. The name must be 4 to 100 characters in length, and can contain letters, digits, and underscores (_).

Interval String No 1

The monitoring frequency. Valid values: 1, 5, and 15. Unit: minutes. Default value: 1.

IspCities String No [{"city":"546","isp":"465"},{"city":"572","isp":"465"},{"city":"738","isp":"465"}]

The detection points. The value is a JSON array. Example: [{"city":"546","isp":"465"},{"city":"572","isp":"465"},{"city":"738","isp":"465"}]. The values of the city field indicate Beijing, Hangzhou, and Qingdao.

Note You can call the DescribeSiteMonitorISPCityList operation to query the detection points. For more information, see DescribeSiteMonitorISPCityList. If you leave this parameter empty, the system randomly selects three detection points.
OptionsJson String No null

The extended options of the protocol that is used by the site monitoring task. The options vary based on the protocol.

AlertIds String No 49f7c317-7645-4cc9-94fd-ea42e122****

The ID of the alert rule. You can call the DescribeMetricRuleList operation to query the IDs of existing alert rules in CloudMonitor. For more information, see DescribeMetricRuleList.

IntervalUnit String No ms

The unit of the monitoring frequency. This parameter and the Interval parameter must be used in pair. For example, you can set this parameter to ms and the Interval parameter to 15000 (15 seconds). Valid values:

  • s: seconds
  • ms: milliseconds

Site monitoring supports the following eight protocols. The following tables describe the extended options specified by the OptionsJson parameter for each protocol.

  • HTTP

Parameter

Type

Description

http_method

String

The HTTP request method. Valid values: GET, POST, and HEAD. Default value: GET.

header

String

The custom HTTP headers that are separated by line feeds (\n).

Each header must comply with the HTTP protocol. Each header must be a key-value pair in which the key and value are separated by a colon (:).

cookie

String

The HTTP cookie that is specified in compliance with the HTTP request standard.

request_content

String

The content of the request. The content can be in the JSON or form format. If this parameter is not specified, the request body is empty.

response_content

String

The expected content of the response. The first 64 bytes of the content returned by the HTTP server are checked during site monitoring.

match_rule

String

0: If the response does not contain the content specified by the response_content parameter, the detection is successful.

1: If the response contains the content specified by the response_content parameter, the detection is successful.

username

String

If the username parameter is specified, the HTTP request contains the basic authentication header.

password

String

The password that is used to authenticate the HTTP request.

time_out

int

The timeout period. Unit: milliseconds. Default value: 5.

max_redirect

int

The maximum number of redirections. The default value is 5 for a detection point that is running on an Elastic Compute Service (ECS) instance and 2 for a detection point that is provided by a carrier.

To disable redirections, set the value to 0.

Valid values: 0 to 50.

  • PING

Parameter

Type

Description

failure_rate

int

If the rate of the failed pings exceeds the value of this parameter, the detection fails and the status code 610 or 615 is returned. The error message of the status code 610 is PingAllFail and the error message of the status code 615 is PingPartialFail.

Default value: 0.1.

ping_num

int

The number of times that the monitored address is pinged. Default value: 20.

Valid values: 1 to 100.

  • DNS

Parameter

Type

Description

dns_server

string

The domain name or IP address of the Domain Name System (DNS) server.

dns_type

string

The type of the DNS records to query. Valid values: A, NS, CNAME, MX, TXT, and ANY.

expect_value

string

The list of expected values. Separate the expected values with spaces.

match_rule

string

The relationship between the list of expected values and the list of DNS results. If the two lists do not meet the specified relationship, the detection fails. Valid values:

Empty string or IN_DNS: The list of expected values is a subset of the list of DNS results.

DNS_IN: The list of DNS results is a subset of the list of expected values.

EQUAL: The list of DNS results is the same as the list of expected values.

ANY: The list of DNS results intersects with the list of expected values.

  • FTP

Parameter

Type

Description

port

int

The port number of the FTP server. If this parameter is not specified, the default value is used. The default port number is 21 for FTP and 990 for FTPS.

username

string

The username that is used to log on to the FTP server. If this parameter is not specified, anonymous logon is used.

password

string

The password that is used to log on to the FTP server.

  • POP3/SMTP

Parameter

Type

Description

port

int

The port number of the POP3 server. The default port number is 110 for POP3 and 995 for POP3S.

username

string

The username that is used to log on to the POP3 or SMTP server.

password

string

The password that is used to log on to the POP3 or SMTP server.

  • TCP/UDP

Parameter

Type

Description

port

int

The port number of the TCP or UDP server.

request_content

string

The content of the request. If the request_format parameter is set to hex, the value of the request_content parameter is parsed in the hexadecimal format.

request_format

string

If the request_format parameter is set to another value, the value of the request_content parameter is sent to the TCP or UDP server as a regular string.

response_content

string

The content of the response. If the response from the TCP or UDP server does not contain the content specified by the response_content parameter, the detection fails.

If the response_format parameter is set to hex, the value of the response_content parameter is parsed in the hexadecimal format.

If the response_format parameter is set to another value, the value of the response_content parameter is parsed as a regular string.

Response parameters

Parameter Type Example Description
Code String 200

The HTTP status code.

Note The status code 200 indicates that the call is successful.
Data Struct

The result of modifying the task.

count Integer 1

The number of site monitoring tasks.

Message String successful

The returned message.

RequestId String 68192f5d-0d45-4b98-9724-892813f86c71

The ID of the request.

Success String true

Indicates whether the call is successful. Valid values:

  • true: The call is successful.
  • false: The call fails.

Examples

Sample requests

http(s)://[Endpoint]/?Action=ModifySiteMonitor
&TaskId=2c8dbdf9-a3ab-46a1-85a4-f094965e****
&TaskName=HanZhou_ECS2
&<Common request parameters>

Sample success responses

XML format

<ModifySiteMonitorResponse>
	  <Message>successful</Message>
	  <RequestId>32E77F32-B86E-4763-A0BB-0311581ABE67</RequestId>
	  <Data>
		    <count>1</count>
	  </Data>
	  <Code>200</Code>
	  <Success>true</Success>
</ModifySiteMonitorResponse>

JSON format

{
	"Message": "successful",
	"RequestId": "32E77F32-B86E-4763-A0BB-0311581ABE67",
	"Data": {
		"count": 1
	},
	"Code": "200",
	"Success": true
}

Error codes

For a list of error codes, visit the API Error Center.