Application Real-Time Monitoring Service:Create a website speed test task

Prerequisites

Before you begin, make sure that you have:

• An activated ARMS service with access to Synthetic Monitoring

• The target website URL (starting with http or https, or in IP address:Port number format)

Create the task

1. Log on to the ARMS console.

2. In the left-side navigation pane, choose Synthetic Monitoring > Scheduled Tests.

3. On the Synthetic Tasks page, click New Task.

4. On the Create Synthetic Task page, click Website Speed.

5. In the STEP1 section, configure the basic settings.

   Parameter	Description
   Task name	A name for the synthetic monitoring task.
   Target Address	The URL of the website to test. Enter a URL that starts with http or https, or an address in the IP address:Port number format.
   Dialing Frequency	Frequency: the interval between test runs. Turn on Custom to restrict the task to specific time periods.

6. In the STEP2 section, select monitoring points.

   Parameter	Description
   Monitoring point type	PC End or Mobile End. Determines the device type used for the test.
   Monitoring Point Group	Select a predefined group: Recommended Monitoring Point Group (commonly used points), All Monitoring Point Group (every available point), or Custom Monitoring Point Group (points you previously saved).
   Select Monitoring Point	Add specific carriers to the Selected Monitoring Point list on the right. To reuse this selection in future tasks, save it as a custom monitoring point group.

   Note

   IPv6 web applications in data centers cannot be monitored.

7. In the STEP3 section, configure advanced settings. These settings are grouped by category.

   Network settings

   Parameter	Description
   IP Protocol	The IP version used to access the website. Automation: randomly tests IPv4 or IPv6. IPv4: tests IPv4 only. IPv6: tests IPv6 only.
   Customize host	Maps domain names to specific IP addresses. Select Polling or Random mode, then enter IP addresses separated by commas (\|). Example: 192.168.1.11,192.168.1.12:www.a.domain. A colon (:) in the entry triggers automatic resolution of the preceding URL.

   Browser behavior

   The Monitoring Related Items parameter controls how the browser behaves during the test:

   Option	Description
   Disable Cache	Clears browser history, temporary files, cookies, saved passwords, HTML forms, and cached resources before loading the page.
   Redirect	Follows and monitors the redirected page. If deselected, redirects return the 651 error code.
   Disable Compression	Prevents the browser from accepting compressed files during the test.
   Auto Scroll	Simulates scrolling to the bottom of the page.
   Ignore Certificate Errors	Skips SSL certificate validation errors during the handshake. Deselect this option to detect certificate issues.

   Timeouts and thresholds

   Parameter	Description	Default
   Monitoring Timeout	Maximum execution time before a timeout error is reported.	40,000 ms
   Maximum Wait Time	Interval at which ARMS checks browser status.	40,000 ms
   Slow Element Threshold	Download time threshold for flagging slow elements. Elements exceeding this value are marked as slow.	5,000 ms

   Request headers

   Parameter	Description
   Custom Header	Adds or modifies request headers. Turn on this option, then choose: Modify Global Packet (modifies headers for all requests) or Modify First Packet (modifies the header of the first request only).

   Hijack detection

   Use these settings to detect DNS hijacking, page tampering, and traffic hijacking.

   Parameter	Description
   Hijack Parameters - DNS Hijack Whitelist	Trusted DNS resolution results. If a resolved IP address or CNAME record is not in this whitelist, the resolution is flagged as hijacked. Format: <domain name>:<matching rule>. Rules can be exact IP addresses, wildcards, subnet masks, or CNAME records. Separate multiple rules with vertical bars (\|). Example: www.aliyun.com:202.0.3.55\|203.3.44.67 -- any IP resolved for this domain other than 202.0.3.55 and 203.3.44.67 is treated as hijacked.
   Hijack Parameters - Page Tampering	Whitelist of expected page elements. Elements not in the whitelist (such as pop-up ads, floating ads, or unauthorized redirects) indicate tampering. Format: <domain name>:<element name>. Wildcards are supported. Separate entries with vertical bars (\|). Example: www.aliyun.com:\|/cc/bb/a.gif\|/vv/bb/cc.jpg.
   Hijack Parameters - Traffic Hijacking	Detects HTTP 302 redirect abuse. Configure Identify Elements (total page element count) and Hijack Identification (keywords to identify hijacking; asterisks are supported).

   Important

   Check the elements that return HTTP status code 302 on the page. Synthetic Monitoring typically monitors the status of the basic documents after the HTTP status code is returned.

   Content validation

   Parameter	Description
   Verify String Blacklist	Strings that must not appear in the page source code. If a blacklisted string is found, the 650 error code is returned. Separate multiple strings with vertical bars (\|).
   Verify String Whitelist	Strings that must appear in the page source code. If a required string is missing, the 650 error code is returned. Separate multiple strings with vertical bars (\|).
   Element Blacklist	Elements to exclude from loading during the test. Do not add basic documents to this list.
   Availability Assertion	Conditions that determine whether the monitoring result is considered available. The test passes only when all specified conditions are met.

   Resource management

   Parameter	Description
   Resource Group	The resource group for the task. For more information, see Create a resource group.

8. Click Create Task.

Result

After the task is created, you are redirected to the Synthetic Tasks page.