Scenarios

This topic describes how to create a monitor to monitor and analyze network quality and performance.

An account can create a maximum of 20 monitors.

Procedure

1. Log in to the management console.
2. Under Management & Deployment, select Cloud Eye.
3. On the Website Monitoring page, click Create Monitor in the upper right corner.
4. (For initial configuration) Select the region where the website monitoring data is stored.
   

   You can change the region that stores your website monitoring data, including your alarm rules, graphs, and exported monitoring data.

5. In the displayed Create Monitor dialog box, set parameters as prompted.
   Figure 1 Create Monitor
   

   Table 1 Parameter description

   Parameter	Description	Example Value
   Name	Specifies the monitor name.	siteMonitor-mfdp
   Type	Currently, the following protocols are supported: HTTP(S), PING, TCP, and UDP. More monitor types are being deployed.	HTTP(S)
   URL	Specifies the address to be monitored. NOTE: To monitor an HTTPS website, enter the protocol header https://. Website monitoring does not support IP addresses in the following private IP address segments: 10.0.0.0–10.255.255.255 172.16.0.0–172.31.255.255 192.168.0.0–192.168.255.255 127.0.0.0–127.255.255.255	www.example.com
   Monitoring Frequency	Specifies the interval for the website monitoring detection engine to detect once. NOTE: Monitoring Frequency can be set to 1 minute, 5 minutes, or 20 minutes.	1 minute
   Checkpoint Location	Currently, website monitoring supports the following checkpoint locations: North China (Langfang), East China (Shanghai), South China (Guangzhou), Southwest China (Guiyang), and South China (Shenzhen).	North China (Langfang), East China (Shanghai), and South China (Guangzhou)
   Request Method	This parameter is available when Monitor Type is set to HTTP(S). Standard HTTP(S) request methods include GET, POST, and HEAD. The POST method can be used to submit content.	HEAD
   Port Number	This parameter is available when Monitor Type is set to TCP or UDP.	8080
   Advanced Settings	Different monitor types have different advanced settings. If Type is HTTP(S), see Table 2. If Monitor Type is TCP, see Table 3. If Monitor Type is UDP, see Table 4.	N/A

   Table 2 HTTP(S) advanced parameters

   Parameter	Description	Example Value
   HTTP Request Header	Specifies the HTTP header required to detect the target website. Each header must be on a separate line. NOTE: If the submitted content is in the key=value format, the value of HTTP Request Header must be Content-Type: application/x-www-form-urlencoded.	key1=value1
   Request Cookies	Specifies the cookie required to detect the target website. Each cookie must be on a separate line.	key1=value1
   String Match	Yes: If the response body contains the specified matched string, the detection succeeds. No: If the response body does not contain the specified matched string, the detection succeeds.	Yes
   Matched String	Specifies the expected HTTP response content.	-

   Table 3 TCP advanced parameters

   Parameter	Description	Example Value
   Request Content Format	The value can be in hexadecimal or text format.	Hexadecimal
   TCP Request Content	Specifies the preset TCP request content.	0xcf
   Matched String Format	The value can be in hexadecimal or text format.	Hexadecimal
   Matched String	Specifies the expected TCP response content.	N/A

   Table 4 UDP advanced parameters

   Parameter	Description	Example Value
   Request Content Format	The value can be in hexadecimal or text format.	Hexadecimal
   UDP Request Content	Specifies the preset UDP request content.	0xcf
   Matched String Format	The value can be in hexadecimal or text format.	Hexadecimal
   Matched String	Specifies the expected UDP response content.	N/A

6. Click OK.