tencent cloud

Feedback

Creating Network Quality Task

Last updated: 2024-07-05 11:40:06
    This document describes how to create a network quality test task to monitor the reliability of the application network and route, DNS resolution accuracy, ICMP latency, and packet loss rate.

    Directions

    Creating a test task

    1. Log in to the CAT console.
    2. On the left sidebar, click Tasks.
    3. Click Create task at the top of the Tasks page.
    4. Configure the basic information as follows:
    Configuration Item
    Description
    Test mode
    Select Regular test.
    Task type
    Select Network quality on the PC or mobile.
    Test address
    Enter the target web application address starting with http:// or https://.
    For example:
    1. Domain: http://www.tencent.com
    2. Domain and port: http://www.tencent.com:80
    Note: You need to enter the port when using TCP or UDP in Ping monitoring.
    Test task name
    Enter a test task name.
    Test frequency
    It can be 1 minute, 5 minutes, 10 minutes, 15 minutes, 30 minutes, 60 minutes, or 120 minutes. For example, if you select 5 minutes, each testing node will be tested once every five minutes.
    Execution time
    The task is performed every day by default. You can also customize an execution plan as needed. For example, you can set to execute a test task between 8:00 AM and 9:00 AM on any specified day of the week.
    Task tag
    CAT can be used with the Tencent Cloud resource tag feature to perform tag-based sub-account authorization and cost allocation.
    5. Configure the testing node as follows: i. Select the method: You can select Recommended testing node group or Custom testing node group (the former contains common nodes). ii. Select testing nodes
    Availability testing nodes: Only network quality and API monitoring tasks are supported. This option is suitable for network quality monitoring, API availability monitoring, and hijacking and blocking detection.
    Scenario-based testing nodes: This option is suitable for page user experience and streaming lag monitoring, availability testing under poor network conditions, CDN selection, and path optimization. It covers global IDC, PC, and mobile testing nodes.
    Recommended testing node group: Commonly used and recommended testing nodes.
    Custom testing node group: Select the region, node type, and testing node on the right box. Node types are as detailed below:
    Testing node Type
    Description
    PC
    IDC
    It is the testing node deployed on the PC to test the PC user experience.
    LastMile
    It is the testing node deployed on the end user's PC to test the end user's experience on the PC.
    Mobile
    It is the location deployed on the mobile phone to test the mobile user experience.
    My testing node group: You can select a common testing node group in Scenario-based testing nodes and click Create testing node group in the bottom-right corner. Then, you can directly select a common testing node you created from My testing node group when creating a task.
    
    
    Suggestions for selection
    IDC and LastMile have different network environments, and the former is more stable than the latter.
    To test the business availability, you can select the more stable IDC.
    To check the access experience and network conditions of end users, we recommend you select LastMile or Mobile to simulate the user access to an application.
    6. Configure the test parameters (optional). By default, the system configures common test parameters. You can also customize test rules as follows:
    Configuration Type
    Configuration Item
    Description
    Default Value
    IP type
    -
    It can be Auto, IPv4, or IPv6.
    Auto
    Ping monitoring
    Protocol type
    It can be ICMP, TCP, or UDP.
    ICMP
    Test timeout period (sec)
    Define the test timeout period. Value range: 0-60 (excluding `0`).
    20 seconds
    Execution interval (sec)
    Define the interval for executing Ping test tasks, which can be 0.5s, 1s, 2s, 3s, 4s, 5s, or 10s.
    0.5s
    Packages
    Enter the number of test data packages.
    4
    Package size (KB)
    Enter the size of the test data package.
    32 KB
    Package split
    Decide whether to split the test data package as needed.
    Split
    DNS monitoring
    Test timeout period (s)
    Define the test timeout period. Value range: 0-45.
    5s
    Query method
    It can be Recursive or Iterative.
    Recursive
    Specify NS server
    It specifies the server for DNS. Enter the NS service address.
    -
    dig command
    Whether to enable the test result in dig command format.
    Disable
    DNS server type
    It can be Auto, IPv4, or IPv6.
    IPv4
    TRACERT monitoring
    Test timeout period (s)
    Define the test timeout period. Value range: 0-300 (excluding `0`).
    60s
    Maximum number of hops
    Enter the number of hops. A route is one hop.
    20
    Hijacking monitoring
    DNS hijacking allowlist
    If the IP from the DNS query is not in the allowlist, hijacking occurred, and the hijacking result can be selected and viewed in the details of the testing statistics. For more information, see Hijacking Monitoring Parameter Description.
    -
    DNS hijacking blocklist
    If the IP from the DNS query is in the blocklist, hijacking occurred, and the hijacking result can be selected and viewed in the details of the testing statistics. For more information, see Hijacking Test Parameter Description.
    -

    Batch creating test tasks

    Note:
    You can create up to 20 test tasks in batch.
    On the Create task page, click + below the Task name and enter the task name and address. The created test tasks will be displayed in the task list.
    
    
    Contact Us

    Contact our sales team or business advisors to help your business.

    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    7x24 Phone Support