---
title: "Subtest Results"
slug: "subtest-results"
description: "Analyze individual subtest performance metrics with the Subtest Results page, featuring agent indicators, alert timelines, and detailed charts."
tags: ["Performance Metrics", "Test Configuration", "Test Results"]
updated: 2026-07-02T04:01:37Z
published: 2026-07-02T04:01:37Z
canonical: "kb.kentik.com/subtest-results"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://kb.kentik.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Subtest Results

This article describes the results pages for individual subtests found under Kentik’s [**Tests**](/v1/docs/tests-page) page.

> [!NOTE]
> **Note:** There are no subtests, and thus no Subtest Results pages, for tests of [**BGP Monitor**](/v1/docs/bgp-monitor-results) type.

![Graph showing average latency and packet loss over time for Amsterdam, Netherlands.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/TCC-subtest-details-page-main.png)

*The Subtest* *Results* *page shows details about an individual subtest.*

The Subtest Results page under the [**Tests**](/v1/docs/tests-page) page provides a granular, drilldown view of a specific agent-to-target connection within a broader synthetic test. It allows you to isolate and analyze performance metrics for a single path over a selected time range.

> [!TIP]
> **Tip**: Subtests are automatically created based on the parent test's configuration (see [**Test Results**](/v1/docs/test-results)). Subtests are not explicitly created by Kentik portal users.

## Subtest Results Page UI

This section describes the UI elements of the results page for an individual subtest.

### Subtest Results Main Controls

- **Subtest Identifier**: A heading at the upper left of the page identifies the test by showing what it is testing from and toward.

> [!NOTE]
> **Notes:** When the from or toward is an agent:
> 
> - An icon to the left of the agent name indicates whether it is a global or private agent.
> - Text below the name displays the cloud region or AS name/number.
> - A green checkmark indicates the agent is active, while a red exclamation mark indicates it is offline.
- **Time Range:** A dropdown menu to select the lookback period (e.g., Last 1 Hour).
- **Latest:** Jumps to the most recent data point.
- **Details Tabs**: A set of tabs on the left (which vary depending on the [**test type**](/v1/docs/test-types)) that provide different test results views for the currently selected time slice.

### **Alert Timeline**

The **Alert Timeline** provides a visual, interactive chart representing your subtest's data points and overall status over the selected time range (see [**Status Time and Scope**](/v1/docs/test-status-reference#status-time-and-scope)). By default, the latest time slice (far right) is selected, and for which details are given in charts in the [**Data Section**](/v1/docs/subtest-results#data-section). Hovering over the chart displays the exact timestamps for specific data points.

### **Data Section**

A unified **Data** section presents the core performance metrics for an individual subtest. Depending on the test type, you can toggle between the following inline tabs:

#### Time Series

The **Time Series** tab displays a set of combination and line charts detailing the performance of this specific subtest over time.

![Subtest details for a Network Mesh test, with graphs showing average latency and packet loss over time.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/TCC-subtest-details-network-mesh.png)

- **Standard Metrics**: Includes Avg Latency (ms), Packet Loss (%), and Avg Jitter (ms), each displaying its Average, Minimum, and Maximum values. Depending on the test, it may also include a Traffic chart detailing inbound and outbound Kbps.
- **Chart Behaviors During Failures**: When a test fails during a given period, the way it plots depends on the cause:
  - **Errors** (e.g., agent/OS error): Results in a gap in the plot for Latency, Jitter, and Packet Loss.
  - **Timeouts**: Results in a gap in the plot for Latency and Jitter, but Packet Loss will spike and be shown as 100%.
- **Test-Specific Metrics**: Depending on the test type, additional charts will appear automatically:
  - **DNS Tests**: Displays DNS Results lozenges and a Resolution Time chart.
  - **HTTP(S) / API Tests**: Displays HTTP Stages Breakdown, Avg HTTP Latency, and HTTP Status Code charts.
  - **Page Load Tests**: Includes the HTTP charts above, plus a CSS Selectors chart showing a count of configured selectors found on the page.

#### Path View

The **Path View** tab graphically represents the hop-by-hop traceroute data specific to this individual subtest path.

![Critical alert showing packet loss and latency issues in network path view.](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/TCC-subtest-details-network-mesh-path-view.png)

#### Waterfall (Page Load Tests)

For a Page Load subtest, the **Waterfall** tab shows the load order and load duration of each element in the DOM (see [**Test Types Reference**](/v1/docs/test-types)).

![](https://cdn.us.document360.io/082e25b5-afce-42d4-8f47-70bd3f1d02b7/Images/Documentation/image(522).png)

- **Filtering**: Enter text in the **Filter** field to filter the resources shown in the table. Choose a scope of either **URL** or **Body** using the dropdown in the upper left. Use the Type Selector to isolate specific resource types (e.g., JavaScript, CSS, image), or toggle **Errors Only**.
- **Visual Phases**: The download for each resource is represented in the **Waterfall** column as a horizontal bar broken into colored segments corresponding to different phases (stalled, DNS lookup, SSL, initial connection, request sent, waiting, content downloaded). Hovering over a bar reveals the exact duration of each phase.

#### Results (Transaction Tests)

The **Results** tab shows the total transaction completion time for a Transaction subtest.

- **Transaction Completion Plot**: Individual transactions are plotted as dots. Passing transactions plot on the upper green PASS line, while failing transactions (timeouts) plot on the lower red FAIL line.
- **Screenshots**: Displays visual captures taken at points specified in your Transaction test script (see [**About Transaction Test Scripts**](/v1/docs/transaction-test-scripts#about-transaction-test-scripts)).

> [!NOTE]
> **Note**: Screenshots will not be present for a given time slice if the health status during that time was Critical).
