The synthetic monitoring feature uses the globally distributed monitoring networks to view, perform, and download network synthetic monitoring on web applications such as websites and servers. This topic describes how to create a cloud dial-up browsing task.


  1. Log on to the ARMS console.
  2. In the left-side navigation pane, click Cloud Dial Test. On the Scheduled Dial Test page, click + Create Scheduled Task in the upper-right corner.
  3. In the Basic Information step, set the Task Name, Task Address, and Task Type parameters and click Next.
    Parameter Description
    Job Name The name of the synthetic monitoring task.
    Task Address The URL of the web application on which you want to perform synthetic monitoring. Addresses starting with http or https are supported. Addresses in ip:port format are also supported.
    Job Type Set Task Type to Browse-IE Full Elements or Browse-Chrome Full Elements (HTTP1.1/2.0).

    Browsing tasks support obtaining user experience data for accessing Web pages in different environments (city carriers, browser versions, operating systems, and so on), and using the generated report analysis to understand the access performance of the pages.

  4. In the Monitoring Points step, perform the following operations:
    1. Set Add Method to Recommended Monitoring Point Group or Custom, and add the monitoring points to the Added Monitoring Points section on the right.
      Note The recommended monitoring point group includes monitoring points in major provinces and cities in China. The custom group includes all monitoring points supported by Alibaba Cloud Dial Test in the world.
    2. Click Next.
  5. In the Monitoring Parameters step, set the parameters and click Next.
    Parameter Description
    IP Address Type The type of the IP address. Valid values:
    • Automatic
    • IPV4
    • IPV6
    Associated Items The monitoring settings of the task. Valid values:
    • Disable Caching: specifies whether cached resources can be loaded when a page is loaded.
    • Return Elements: specifies whether to return the elements on the page.
    • Redirection: specifies whether to continue browsing after a redirection occurs.
    • Disable Compression: uses the Accept-Encoding field to determine whether to accept compressed files.
    • Automatic Scrolling: specifies whether to automatically scroll up and down the screen to load a page.
    • Ignore Certificate Errors: specifies whether to ignore certificate errors during certificate verification in the SSL handshake and continue browsing.
    • Filter Out Invalid IP Address: specifies whether to filter out the invalid IP address, which is
    QUIC Version The QUIC version.
    QUIC Request Element Domain The domain name of the QUIC request element.
    Advanced Settings
    Return Request Header The type of the request header to return. Valid values:
    • Return Basic Document: The HTML request header of the page is returned.
    • Return All Elements: All element resources of the page are returned.
    • None
    Return Response Header The type of the response header to return. Valid values:
    • Return Basic Document: The HTML response header of the page is returned.
    • Return All Elements: All element resources of the page are returned.
    • None
    Environment ID The version of the framework. You can select one or more framework versions.
    • Framework 2.0
    • Framework 3.0
    • Framework 3.5
    • Framework 4.0
    • Framework 4.5
    Note When the selected monitoring points do not conform to the selected framework versions, an error is reported. Valid values:
    Custom Host Select a custom host mode (Round Robin or Random ), and then enter a custom host in the field.

    Custom Host Format: You can enter multiple IP addresses. Separate each IP address with a comma (,). Example: ipv4:,|[8080]

    Note If a colon (:) is used, a URL before the colon (:) is automatically resolved.
    Custom Header Specifies whether to add or modify some field values in the request header. Valid values:
    • Modify First Packet: modifies the header of the first request packet in the browse task.
    • Modify All Packets: modifies the headers of all packets.
    • Off: does not modify the headers of packets.
    Enter a custom header in the text box. Custom Header Format: You can specify multiple fields. Separate multiple fields with vertical bars (|). Example:|
    Element Blacklist The elements not to be loaded in the page loading process.
    Element whitelist Elements in the element whitelist should be included in the specified element blacklist range. Elements in the element whitelist will be loaded normally during the loading process.
    Process ID The name of the process contained in the task manager on the host that runs tasks. If a process whose name is not contained in the task manager, an error is reported.
    First Screen ID By default, the 600 pixel height is used to determine the first screen. You can also determine the first screen based on the URL and MARK logo.
    • URL: When an element is loaded, the first screen rendering is considered to be complete, reaching the first screen inspection standard.
    • MARK: The browser parses to a page tag and considers it to meet the first screen inspection standard.
    Verification String Blacklist If the source code returned by the client contains any of the specified strings, an error is reported. Separate multiple strings with vertical bars (|).
    Verification String Whitelist If the source code returned by the client does not contain any of the specified strings, an error is reported. Separate multiple strings with vertical bars (|).
    Monitoring Timeout The default time is 60 seconds. After the Onload event, the program periodically queries the browser's working status, and if it is busy, it continues to wait. If the browser status remains busy until the specified time after n cycles, the task is stopped and data is reclaimed. If it is idle, browsing is considered complete.
    Waiting Period The period that ARMS waits to check the status of the browser. The default waiting period is 3.8 seconds. ARMS checks the status of the browser at intervals of the specified period.
    Slow Element Threshold The default value is 5 seconds. That is, if the total download time of this element exceeds 5 seconds, it will be defined as a slow element and will be reflected in the scatter details.
    Hijacking parameters
    DNS hijacking whitelist When a domain name (for example, is resolved, the resolved IP address or CNAME is not in the DNS hijacking whitelist, the user will fail to access or return a destination IP address that is not Aliyun. If the IP address or CNAME in the resolution result is in the DNS whitelist, it will be deemed that no DNS hijacking has occurred.

    Format: Domain Name: Matching Rule. Matching rules support IP, IP wildcard, subnet mask, and CNAME. You can enter multiple matching rules. Separate multiple matching rules with vertical bars (|). For example,| indicates that all IP addresses of the domain name except and are hijacked.

    Page Tampering The monitoring page appears that elements other than the domain name settings belong to the page being tampered with. Common forms of expression are pop-up ads, floating ads, jumps, etc.

    Format: Domain Name: Element. You can enter wildcards for elements. You can enter multiple elements. Separate multiple elements with vertical bars (|). For example,|/cc/bb/a.gif|/vv/bb/cc.jpg indicates that all elements in the domain name except the base document, /cc/bb/a.gif, and /vv/bb/cc.jpg are tampered with.

    Traffic hijacking Classified statistics for 302 jumps when browsing pages.
    Notice You must confirm that there are 302 elements in the page. Dial tasks generally monitor what happens after the underlying document is 302.
    • Identify Elements: Sets the total number of elements on the browse page.
    • Hijacking ID: specifies the key information for matching. Enter a hijacking judgment keyword or key element, which is allowed to contain an asterisk (*).
  6. In the Monitoring Cycle step, set the parameters and click Next.
    Parameter Description
    Monitoring Frequency The intervals at which the synthetic monitoring task runs.
    Advanced Settings
    Start Execution Time The time to start running the synthetic monitoring task. This parameter is valid only when the synthetic monitoring task runs at long intervals. The value of this parameter cannot be greater than the value of the Monitoring Frequency parameter.
    Evenly Distribute Monitoring Samples Offset = Number of minutes in a cycle/Number of carriers. The earliest delivery time of each carrier is the value of the Start Execution Time parameter plus the offset.

    Distributing monitoring samples evenly can be used to distribute dialing tasks to avoid an instantaneous increase in the traffic of the monitoring target website due to simultaneous dialing. We recommend that you select this parameter in scenarios with multiple monitoring points and high frequencies.

  7. In the Alert Parameter step, perform the following operations:
    1. Select an alert metric and turn on the switch on the right side of the alert metric.
    2. Set an alert rule. For example, Alert on the first screen: If the first screen duration of a task is greater than 7s, an alert is triggered.
    3. Select a notification policy from the Notification policy drop-down list.
      You can click Create Notification from the drop-down list. In the Create Notification Policy panel, set Notification Name, Notification Person, and Notification Method to create a notification policy.
    4. Click Next.
  8. In the Preview & Publish step, confirm the parameters and click Complete.
    Then, the Scheduled dial test page appears.