Help Center> Cloud Eye> User Guide> Website Monitoring> Introduction to Website Monitoring
View PDF

Introduction to Website Monitoring

Scenarios

Website monitoring is used to simulate users' access to remote servers and continuously monitor the remote server status, such as availability and connectivity.

Checkpoint locations in North China (Langfang), East China (Shanghai), South China (Guangzhou), Southwest China (Guiyang), and South China (Shenzhen) are supported. More checkpoint locations will be available soon.

  • Website monitoring is free.
  • The website monitoring function is available in the CN North-Beijing1 region. If you want to use this function in other regions, the user group that you belong to must be assigned permissions for cn-north-1 [CN North-Beijing1] through IAM.
    Figure 1 Change Object

Advantages

  • You can create, modify, disable, enable, or delete monitors.
  • The configuration is simple and quick, allowing you to improve efficiency and save resources that you would otherwise use to configure complex open source products.
  • You receive notifications of website exceptions in real time.

Metrics

Table 1 Website monitoring metrics

Metric

Description

Response Time

The time taken by a website to respond to a request (from the time when the connection between the monitoring location and the website is established to the time when the monitoring location receives the first byte of the response message)

Unit: ms

Availability

Availability data is collected hourly. The Availability graph can be viewed one hour after the creation of a monitor.

Availability = (Number of the total detections per hour – Number of exception detections per hour)/Number of total detections per hour x 100%

Packet Loss Ratio

Ratio of the number of lost packets to the total number of packets transmitted

HTTP Response Code

Response status reported by the server

Available Monitoring Locations

Number of available monitoring locations

Available Monitoring Location Percentage

Percentage of available monitoring locations

Available Monitoring Location Percentage = Number of available monitoring locations/Number of all monitoring locations x 100%
  • Response Time, Availability, Available Monitoring Locations, and Available Monitoring Location Percentage are applicable to HTTP(S), Transmission Control Protocol (TCP), User data protocol (UDP), and Packet Internet Groper (PING). Packet Loss Ratio applies only to PING. HTTP Response Code applies only to HTTP(S).
  • Standard network protocols, such as Post Office Protocol version 3 (POP3), Simple Mail Transfer Protocol (SMTP), Domain Name System (DNS), and File Transfer Protocol (FTP), will be supported later to detect Internet service availability.

Protocols Supported

Table 2 Protocol description

Protocol

Description

HTTP(S)

Used to perform HTTP(S) detection on the specified URL or IP address.

Three request methods: GET, POST, and HEAD are supported. In Advanced Settings, you can specify HTTP Request Header and Request Cookies of the above request methods.

PING

Used to test connectivity to a specified URL.

TCP

Used to perform TCP detection on the specified port.

In Advanced Settings, you can specify TCP Request Content and its response content can be matched.

UDP

Used to perform UDP detection on the specified port.

In Advanced Settings, you can specify UDP Request Content and its response content can be matched.
Parent topic: Website Monitoring