Analyse: Custom chart

Overview

Use this page to build a custom overlay chart from a completed run's measurement timings or performance counters. The chart combines one or more data series on a shared time axis, letting you correlate transaction response times with system-level metrics from the same run without leaving the Analyse section.

The page depends on two upstream entities: a datasource configured in Configuration: Datasources and at least one completed run visible in Testing: Test Runs. Once you build a chart you want to keep, you can save it for later retrieval through Analyse: Saved charts, or open the full Analysis workbench for deeper inspection.

On this page you choose between single-overlay and compare-runs modes, pick the datasource and run, assign a measurement timing or performance counter to the Y-axis, and view the result in the Overlay panel. The chart canvas remains empty until both Datasource and Run are selected.

Key concepts

• Datasource - A connection record that points to a load test data store. The Datasource dropdown is populated from the datasources configured in Configuration: Datasources. (related: Configuration: Datasources)
• Run - A single completed execution of a load test from which metrics are read. Only runs associated with the selected datasource appear in the Run dropdown. (related: Testing: Test Runs)
• Measurement timing - A transaction-level response time recorded at intervals during a run. Selecting a specific timing narrows the chart to that transaction; All transactions aggregates across the full workload.
• Performance counter - A system-level metric such as CPU or memory sampled from a monitored machine during a run. Available only when PerfCounter collection was enabled for the run's agents before the test ran. (related: Configuration: Systems Under Test: PerfCounter Settings)
• Overlay - The rendered chart in the right panel that plots all selected data series against a shared time axis, making cross-series correlation visible in a single view.

When to use it

• You want to correlate transaction response times with server resource usage recorded during the same run.
• You need to inspect how a specific transaction's timing changed over the full duration of a run.
• You are comparing metrics from two separate runs to identify a performance regression.
• You want to overlay a performance counter such as CPU on top of a transaction timing on a single chart.
• You are migrating from the legacy Analyzer tool and need to replicate a custom chart you built there.
• You need a quick ad-hoc chart not already surfaced in the standard Analysis or Dashboard views.

Before you begin

• At least one datasource must be configured. Create or verify it on Configuration: Datasources.
• At least one completed load test run must exist and be associated with that datasource. Verify it on Testing: Test Runs.
• If you plan to plot performance counters on the Y-axis, confirm that PerfCounter collection was enabled for the run's agents before the test ran. Check the settings on Configuration: Systems Under Test: PerfCounter Settings.

Common workflows

Build a transaction timing chart for a single run

Persona: Load test operator reviewing a completed run

1. Confirm Datasource category is set to the correct category, then select your target data store from the Datasource dropdown.

- Expect: The Run dropdown activates and lists the completed runs associated with the selected datasource.

2. Select the target completed execution from the Run dropdown.

- Expect: The OVERLAY panel canvas activates and renders the default Y1 series using All transactions timing.

3. Confirm the Y1 · left axis toggle is set to Transaction, then select a specific transaction from the Y1 · measurement timing dropdown.

- Expect: The chart redraws to plot only the chosen transaction's response time across the run's full duration.

Verify: The OVERLAY panel shows a line chart on a shared time axis with the chosen transaction's timing on the Y1 left axis. The Y-axis label reflects the selected transaction name and the chart spans the full run duration.

Steps

Step 1

Navigate to Custom chart under the Analyse section to open the chart builder.

Expected result: The page loads with the SELECTION panel on the left and an empty OVERLAY panel on the right. The Datasource and Run dropdowns show placeholder text, and the overlay canvas displays the message 'Pick a datasource and a run to build a chart.'

This is the starting point for building any custom overlay chart; the SELECTION panel must be completed before the chart canvas activates in the OVERLAY panel.

• Single overlay is the active mode by default; switch to Compare runs if you need to plot two runs side by side.
• Datasource category is pre-set to LoadAndPerformance; change it only if your datasource belongs to a different category.
• Y1 · left axis defaults to Transaction; toggle to Performance counter to plot a system-level metric on the Y-axis instead.
• Y1 · measurement timing defaults to All transactions; leave it here to aggregate all transactions or narrow it to a single named transaction.

Field reference

| Field | Purpose | Format / Validation | Required | Default |

|---|---|---|---|---|

| Datasource category | Filters the Datasource dropdown to a category of data stores. Leaving it at the default LoadAndPerformance covers standard load test results; change it only if your data resides in a different category of store. | Dropdown | No | LoadAndPerformance |

| Datasource | Selects the data store from which the Run list is populated. You must select a datasource before the Run dropdown activates. Choosing a different datasource resets the Run selection and clears the overlay canvas. | Dropdown; values come from the datasources available under the selected Datasource category. | No | - |

| Run | Selects the specific completed test execution to draw data from. Choosing a run that captured more named transactions gives you more options in Y1 · measurement timing. The chart canvas activates only after a run is selected. | Dropdown; values are the completed runs associated with the selected datasource. | No | - |

| Y1 · measurement timing | Selects which transaction timing to plot on the Y1 left axis when the axis type is set to Transaction. Leaving it at All transactions plots the aggregate across the full workload; selecting a named transaction focuses the chart on that single measured endpoint, removing noise from other flows. | Dropdown; values are the transaction names recorded in the selected run, plus All transactions. | No | All transactions |

Controls reference

Single overlay

Sets the chart mode to a single run. All series on the overlay canvas are drawn from the one run selected in the Run dropdown.

When to use: Use when you want to correlate multiple metrics within a single run without comparing against another run.

Side effects: Mode change only; no data is modified. The OVERLAY panel re-renders using only the selected run's data.

Compare runs

Switches the SELECTION panel to a two-run layout so a second run can be selected and its metrics plotted alongside the first on the shared time axis.

When to use: Use when you need to identify regressions or improvements by overlaying the same metric from two different runs.

Side effects: Mode change only; no data is modified. The SELECTION panel expands to expose a second Run dropdown.

Transaction

Sets the Y1 left axis to plot a measurement timing. The Y1 · measurement timing dropdown becomes active and defaults to All transactions.

When to use: Use when you want to chart response times for one or more measured transactions.

Side effects: Axis-type change only; the Y1 · measurement timing dropdown appears. Any previously selected performance counter for Y1 is cleared.

Performance counter

Sets the Y1 left axis to plot a system-level performance counter instead of a transaction timing. The Y1 · measurement timing dropdown is replaced by a counter selector.

When to use: Use when you want to chart a resource metric such as CPU or memory, optionally alongside transaction data from another axis.

Side effects: Axis-type change only; the Y1 · measurement timing dropdown is replaced by a counter selector. Any previously selected timing for Y1 is cleared.

Analysis workbench

Navigates to the Analysis workbench, which provides the full built-in analysis environment for the platform.

When to use: Use when you need to move from a custom chart into the structured analysis environment for deeper inspection of the same run.

Side effects: Navigation action; leaves the Custom chart page. Any chart configuration not yet saved is lost.

Verify the result

After selecting both a Datasource and a Run, the OVERLAY panel renders a line chart on a shared time axis with your chosen series visible. The Y-axis label reflects the measurement timing or performance counter assigned to Y1, and the chart spans the full duration of the selected run. If the OVERLAY panel remains blank after both dropdowns are filled, confirm that the selected run contains recorded data; a run aborted before data collection started will appear in the Run list but will produce an empty chart. If the Y1 · measurement timing dropdown shows only All transactions with no named entries, the load profile used for that run did not define named transaction segments.

Troubleshooting

• Symptom: The Datasource dropdown is empty after setting the category. Fix: Confirm that at least one datasource of that category exists on Configuration: Datasources and that your account has read access to it.
• Symptom: The Run dropdown shows no options after selecting a datasource. Fix: Verify that at least one completed run exists for that datasource on Testing: Test Runs.
• Symptom: The OVERLAY panel stays blank after selecting both a datasource and a run. Fix: Check that the selected run captured data; a run stopped before the data collection phase appears in the Run list but yields no chart.
• Symptom: No performance counters appear when Performance counter is selected for the Y1 axis. Fix: Confirm that PerfCounter collection was enabled for the run's agent machines before the test ran; see Configuration: Systems Under Test: PerfCounter Settings.
• Symptom: The Y1 · measurement timing dropdown shows only All transactions with no named entries. Fix: The load profile used for this run did not define named transactions; use All transactions or re-run the test with a profile that includes named transaction segments.

Related articles

• Prerequisite: Configuration: Datasources - a datasource must exist and be accessible before the Datasource dropdown is populated
• Prerequisite: Testing: Test Runs - a completed run must exist before the Run dropdown is populated
• Next step: Analyse: Saved charts - save and retrieve custom charts built on this page
• See also: Analyse: Analysis - structured built-in analysis views over the same run data
• See also: Configuration: Systems Under Test: PerfCounter Settings - enable performance counter collection so counters are available on the Y-axis