2.3 Test Configuration

Overview

ThousandEyes uses synthetic tests to monitor network and application performance. These tests run from various vantage points, including Cloud Agents, Enterprise Agents, and Endpoint Agents. This section focuses on configuring Cloud and Enterprise Agent tests.

flowchart TB
    A(Cloud and Enterprise<br/>Agent Tests) --- F[Routing]
    A --- B[Network]
    A --- C[DNS]
    A --- D[Voice]
    A --- E[Web]
    F --- F1(BGP)
    B --- B1(Agent-to-Server)
    B --- B2(Agent-to-Agent)
    C --- C1(DNS Server)
    C --- C2(DNS Trace)
    C --- C3(DNSSEC)
    D --- D1(RTP Stream)
    D --- D2(SIP Server)
    E --- E1(HTTP Server)
    E --- E2(Page Load)
    E --- E3(Transaction)
    E --- E4(API)
    E --- E5(FTP Server)
              subgraph LAYERS
            B
            C
            D
            E
            F
          end
                   subgraph TESTS
                F1
                B1
                B2
                C1
                C2
                C3
                D1
                D2
                E1
                E2
                E3
                E4
                E5
                end

ThousandEyes tests are organized into layers, similar to the OSI model, to provide a structured view of test results. This layered approach helps correlate information and isolate problems more effectively. For example, you can analyze network-specific metrics in the Network layer view and then correlate them with HTTP metrics from the same test round to determine if a network issue is impacting a web page.

Primary methods for configuring tests include:

• Standalone Tests: Create tests from scratch, configuring all settings manually.
• Test Templates: Use pre-configured templates to quickly deploy tests for common use cases.

For more information on test templates, see the Test Templates documentation.

Additional resources for test configuration and analysis:

• Getting Started with Cloud and Enterprise Agent Tests
• Layers and Test Types
• Test Result Interpretation
• Test Settings
• Using the Path Visualization View
• Getting Started with Views

Configuration instructions for each test type are linked in the respective sections below.

BGP Tests

BGP tests operate at the routing layer to monitor BGP prefix reachability and path changes from multiple vantage points on the internet. Key features include:

• Automatically monitor relevant BGP prefixes based on the target of other test types like HTTP Server or Network tests
• Specify a custom prefix and prefix length in CIDR notation to monitor
• Include covered (more specific) prefixes of the configured prefix
• Use ThousandEyes' public BGP monitors which peer with routers all over the internet
• Set up private BGP monitors to peer directly with your own routers for an internal view

BGP Test Configuration

1. Navigate to Cloud & Enterprise Agents > Test Settings
2. Click Add New Test > Select Routing layer and BGP
3. Enter a Test Name and the Target Prefix in CIDR notation (e.g. 192.0.2.0/24)
4. Optionally check Include covered prefixes to monitor more specific prefixes
5. Select Public or Private BGP Monitors, or both
6. Configure Alert Rules if desired
7. Click Create New Test

The target prefix will now be monitored from the selected BGP vantage points. The BGP Route Visualization view shows the AS path from each monitor to the prefix.

BGP Test Resources

• Inside-Out BGP Visibility
• Using the BGP Route Visualization View

Network Tests

ThousandEyes provides two primary types of network tests: agent-to-server and agent-to-agent. Both test types offer two views:

1. Overview: Displays data on packet loss, latency, jitter (mean deviation of latency), path MTU, and bandwidth (agent-to-server and Enterprise Agents only). Agent-to-agent tests also show throughput.

2. Path Visualization: Provides a traceroute-like map of each router in the path from agent to target, including IP, MPLS, and routing information about each node and link.

Agent-to-Server Test Configuration

To configure an Agent-to-Server network test:

1. Navigate to Cloud & Enterprise Agents > Test Settings
2. Click Add New Test and select Network Layer then Agent-to-Server

3. Configure the following settings in the Basic Configuration tab:

   • Target: Enter a domain name or IP address
   • Protocol: Choose TCP or ICMP
   • Port: Specify the target port number (for TCP only)
   • Path Trace Mode: Select In Session to perform path trace within an established TCP session
   • Agents: Select Cloud and/or Enterprise Agents to run the test
   • Alerts: Enable and configure alert rules as needed

4. Configure Advanced Settings:

   • Perform bandwidth measurements: Available for Enterprise Agents only
   • Perform MTU measurements: Determines path maximum transmission unit in Path Visualization
   • Collect BGP data: Enables BGP Path Visualization View
   • Transmission Rate: Option to enforce fixed packet rate
   • No. of Path Traces: Adjust the number of path trace packets (1-10)
   • Ping Payload Size: Set payload size for End-to-End metric probes (0-1400 bytes)
   • DSCP selector: Set the Differentiated Services Code Point for QoS handling

Agent-to-Agent Test Configuration

To configure an Agent-to-Agent network test:

1. Follow steps 1-2 from the Agent-to-Server configuration

2. In the Basic Configuration tab, set:

   • Target Agent: Select a ThousandEyes Enterprise Agent
   • Agents: Choose source Enterprise Agents
   • Direction: Specify network measurement direction (Source to Target, Target to Source, or Both)
   • Protocol: Select TCP or UDP
   • Enable Throughput: Option to perform throughput measurements
   • Path Trace Mode: Configure as in Agent-to-Server tests

3. In the Advanced Configuration tab, set:

   • Server Port: Specify port number on the Target Agent
   • MSS: Set Maximum Segment Size (Auto or Manual, 30-1400 bytes)
   • Collect BGP data: As in Agent-to-Server tests
   • Transmission Rate: As in Agent-to-Server tests
   • No. of Path Traces: As in Agent-to-Server tests
   • Payload Size: Set packet size for network and throughput measurements
   • DSCP selector: As in Agent-to-Server tests

Network Test Resources

• Network Test Overview
• The Dual Origin of Network Test Results

DNS Tests

ThousandEyes offers three main types of DNS tests:

1. DNS Server Test: Measures availability and performance of specific DNS servers
2. DNS Trace Test: Traces the full DNS resolution path for a domain
3. DNSSEC Test: Verifies DNSSEC signatures and the chain of trust

DNS Test Configuration

To configure a DNS Server test:

1. Navigate to Cloud & Enterprise Agents > Test Settings
2. Click Add New Test and select DNS Layer then DNS Server

3. Configure the following settings:

   • Domain: Enter the domain name to query
   • Record type: Select the DNS record type (A, AAAA, CNAME, MX, NS, TXT, etc.)
   • DNS Servers: Specify target DNS servers or use Lookup Servers to populate with authoritative nameservers
   • Interval: Set test frequency
   • Agents: Select Cloud and/or Enterprise Agents to run the test
   • Alerts: Enable and configure alert rules as needed

4. Advanced Settings:

   • Send Recursive Queries: Option to send recursive queries to target servers
   • Network measurements: Enable associated Network test for target server(s)

DNS Test Resources

• DNS Tests

Voice Tests

ThousandEyes provides two types of voice tests:

1. RTP Stream Test: Evaluates VoIP call quality and performance
2. SIP Server Test: Assesses SIP server performance and availability

RTP Stream Test Configuration

To configure an RTP Stream test:

1. Navigate to Cloud & Enterprise Agents > Test Settings
2. Click Add New Test and select Voice Layer then RTP Stream

3. Basic Settings:

   • Target: Select an Enterprise Agent or Cloud Agent as the endpoint
   • Interval: Set test frequency
   • Agents: Choose source agents

4. Advanced Settings:

   • Server Port: Specify port for incoming RTP sessions
   • Codec: Select codec name and associated bit rate
   • Duration: Set test duration in seconds
   • De-jitter Buffer Size: Configure buffer size to mitigate delay variations
   • Collect BGP data: Enable BGP Path Visualization
   • No. of Path Traces: Set number of path trace packets (1-10)
   • DSCP: Set Differentiated Services Code Point for traffic prioritization

SIP Server Test Configuration

To configure a SIP Server test:

1. Follow steps 1-2 from the RTP Stream configuration

2. Basic Settings:

   • SIP Server: Enter domain name or IP address of the SIP server
   • SIP Proxy: Enable and configure SIP Proxy if needed
   • Protocol: Choose TCP or UDP
   • Port: Specify SIP service listening port

3. Advanced Settings:

   • Perform SIP Register: Enable/disable SIP registration
   • User: Set username for SIP registration
   • Auth User: Configure alternative username for authentication
   • Password: Provide authentication password
   • Desired status code: Specify SIP status code for successful test
   • Verify Headers: Configure header verification using literal text or POSIX regex

Voice Test Resources

• Voice Tests

Web Tests

ThousandEyes offers three main types of web tests:

1. HTTP Server Test: Measures basic availability and response time of web servers
2. Page Load Test: Evaluates full page load experience, including all page elements
3. Transaction Test: Simulates multi-step user interactions like logins or checkouts

Web Test Configuration

To configure a Page Load test:

1. Navigate to Cloud & Enterprise Agents > Test Settings
2. Click Add New Test and select Web as the Layer and Page Load as the Test Type

3. Basic Configuration:

   • URL: Enter the target URL, domain name, or IP address
   • Interval: Set test frequency
   • Agents: Select Cloud and/or Enterprise Agents to run the test

4. Advanced Settings:

   • HTTP Server Timing: Configure timeout and target time for view
   • Page Load Timing: Set timeout and target time for view
   • Proxy Settings: Configure direct, agent proxy, or specific proxy
   • HTTP Authentication: Set up Basic, NTLMv2, Kerberos, or OAuth authentication
   • HTTP Request: Configure HTTP version, window size, SSL version, and more
   • Custom Headers: Add custom HTTP headers
   • HTTP Response: Set desired status code, verify content, and limit download size
   • Client Certificate: Configure client-side SSL certificates

Web Test Resources

• Web Layer Tests
• When to Use a Page Load Test

Sample Questions

2.3 Question 1

Refer to the exhibit. Which setting should be enabled for this Network Agent to Server test to avoid test traffic being detected by firewalls as malicious?

• A) Path Trace Mode: In Session
• B) Protocol: TCP
• C) Port: 5000
• D) Probing Mode: Force SYN

2.3 Question 2

Refer to the exhibit. A network admin has been tasked with monitoring the IPv6 record and name server resolution times with different agents. Select the two actions that the engineer must take to meet the requirements.

• A) Create a DNS Server test monitoring the A record
• B) Create a DNS Server test monitoring the AAAA record
• C) Create a DNS Trace test monitoring the ANY record
• D) Create a DNS Server test monitoring the NS record
• E) Create a DNS Trace test monitoring the NS record

2.3 Question 3

An engineer is trying to configure a Page Load test and is trying to assign the east1-agent-1 to run it, but cannot see that agent listed. What is the reason that the designated agent does not appear?

• A) The agent is not running
• B) The agent is disabled
• C) The agent is still registering
• D) The agent does not support Page load tests

2.3 Question 4

Employees and customers of a retail company are experiencing performance issues with the store website, such as slowness during the login process or failure when adding items to the cart. Which test type is the most useful for identifying the root cause of these problems?

• A) HTTP Server test type
• B) Page Load test type
• C) Transaction test type
• D) Agent-to-server test type
• E) DNS Server test type
• F) Agent-to-agent test type

2.3 Question 5

To monitor communication and measure network performance from branch offices in San Francisco and Texas to the data center in North Virginia, which combination of test type and target is the most appropriate?

• A) Agent-to-server test type and Cloud Agent
• B) Cloud Agent and HTTP Server
• C) Enterprise Agent and Agent-to-agent test type
• D) HTTP Server and DNS Server
• E) Agent-to-server test type and DNS Server