How to test website speed-Application Real-Time Monitoring Service(ARMS)-阿里云帮助中心

Synthetic monitoring helps you understand your online service's network conditions, performance, and user experience to ensure business stability. This topic describes how to create a Website Speed task.

Important

Starting from June 1, 2024, ARMS Synthetic Monitoring no longer supports activating pay-as-you-go billing or purchasing subscription resources. For more information, see Product Change: Discontinuation of Synthetic Monitoring Activation.

Log on to the ARMS console.
In the left-side navigation pane, choose Synthetic Monitoring > Scheduled Tests. On the Synthetic Tasks page, click New Task.
On the Create Synthetic Task page, click Website Speed.

In the STEP1 section, configure the following parameters.

Parameter	Description
Task name	The name of the synthetic monitoring task.
Target address	The address of the web application to monitor. The address can start with `http` or `https`, or be in the `ip:port` format.
Frequency	Frequency: Select how often the task runs. Custom Period: Turn on the Custom Period switch to specify when the task runs each day.

Select detection points in the STEP2 section.

Parameter	Description
Monitoring point type	Valid values: PC End and Mobile End.
Monitoring Point Group	Recommended Monitoring Point Group: The group contains the common detection points recommend by the system. All Monitoring Point Group: The group contains all detection points supported by Synthetic Monitoring. Custom Monitoring Point Group: The group contains the frequently used detection points. Note You cannot monitor IPv6 web applications in data centers.
Select Monitoring Point	Add the carriers that you want to monitor to the Selected Monitoring Point section on the right. Note You can save the carriers added in the Selected Monitoring Point section to a custom detection point group. This way, you can quickly select detection points when you create a synthetic monitoring task.

In the STEP3 section, configure advanced settings.

Parameter	Description
IP protocol	The IP protocol used to access the server. Auto: Randomly tests the performance of IPv4 or IPv6 servers. IPv4: Tests the performance of IPv4 servers. IPv6: Tests the performance of IPv6 servers.
Monitoring options	Select the monitoring options for the task: Disable cache: Clears the browser cache before each test run. This includes browsing history, temporary files, cookies, saved passwords, and web form information. Cached resources are not loaded. Redirect: If you select this option, the task follows HTTP redirects to the final destination page. If you clear this option, the task does not follow redirects and reports the `651 page has been redirected` error if a redirect is encountered. Disable compression: Prevents the task from accepting compressed files. Auto scroll: Simulates scrolling down the page until the scrollbar reaches the bottom. Ignore certificate errors: Ignores certificate errors that occur during the SSL handshake, allowing the browser to continue the test. Disable this option to monitor for SSL certificate errors.
Monitoring timeout	The maximum execution time for the task. If the task exceeds this duration, it reports a timeout error. Default: 40,000 ms.
Maximum wait time	The maximum time the browser waits for the page to complete loading. Default: 40,000 ms.
Slow element threshold	An element is considered slow if its total download time exceeds this threshold. Default: 5,000 ms.
Custom header	Turn on this switch to add or modify fields in the request header. Modify all packets: Modifies the header for all requests. Modify the first packet: Modifies the header of only the first request in the browsing session.
Custom host	Select a custom host mode (round-robin or random), and then enter the custom host in the text box. Format: You can enter multiple IP addresses separated by commas (,). Example: `192.168.1.11,192.168.1.12:www.a.domain`. Note The domain after the colon (:) is resolved to one of the IP addresses specified before the colon.
DNS hijack whitelist	When a domain name (for example, www.aliyun.com) is resolved, if the resolved IP address or CNAME is not on the DNS hijack whitelist, it is flagged as a hijack. If the resolved IP address or CNAME is on the DNS hijack whitelist, the resolution is considered valid. Format: `domain:match_rule`. The part before the colon (:) is the domain to check, and the part after the colon is the matching rule. Matching rules support exact IPs, IP wildcards, subnet masks, and CNAMEs. You can specify multiple matching rules and separate them with vertical bars (\|). For example, `www.aliyun.com:202.0.3.55\|203.3.44.67` indicates that for the www.aliyun.com domain, any resolved results other than 202.0.3.55 and 203.3.44.67 are considered hijacked.
Page tampering	If an element that is not on the configured whitelist appears on the page, it is considered page tampering. Common signs include pop-up ads, floating ads, and redirects. Format: `domain:element`. The part before the colon (:) is the domain to check, and the part after the colon is the element name to match. Elements support wildcards. You can specify multiple elements and separate them with vertical bars (\|). For example, `www.aliyun.com:\|/cc/bb/a.gif\|/vv/bb/cc.jpg` indicates that for the www.aliyun.com domain, any elements other than the base document, /cc/bb/a.gif, and /vv/bb/cc.jpg are considered page tampering.
Traffic hijacking	Classifies and aggregates statistics for 302 redirects that occur while you browse the page. Important This setting monitors 302 redirects for individual elements on a page, not just the base document. Identify elements: Set the total number of elements on the page. Hijack identification: Set the key information to match. Enter the keyword or key element used to determine hijacking. Asterisks (*) are allowed.
Verification string blacklist	A verification string is any string in the page source code. If the source code returned by the client contains any string in the blacklist, the `650 Verification string failed` error is reported. Separate multiple strings with vertical bars (\|).
Verification string whitelist	A verification string is any string in the page source code. The source code returned by the client must contain all strings in the whitelist. Otherwise, the `650 Verification string failed` error is reported. Separate multiple strings with vertical bars (\|).
Element blacklist	The task does not request or load any element on this blacklist. Important Do not add the base document to the element blacklist.
Availability assertion	Defines the conditions that a response must meet for the test run to be considered available.
Resource group	Select the resource group to which the task belongs. For information about how to create a resource group, see Create a resource group.

Click Create a task.

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