---
title: "Reports | Speedscale Docs"
description: "Explore Speedscale's Reports page to analyze replay results, view AI-generated summaries, and access detailed insights on performance and recommendations."
canonical: "https://docs.speedscale.com/guides/reports/"
---

[Documentation index](https://docs.speedscale.com/guides/llms.txt) | [Markdown](https://docs.speedscale.com/guides/reports/index.md) | [Canonical page](https://docs.speedscale.com/guides/reports/)

# Reports

Reports are an artifact of replays and a new report is created for every one.

After a replay is run the associated report will detail how successful the

replay was. Starting at the [reports page](https://app.speedscale.com/reports)

you can find reports sorted with the most recent at the top.

Use search to find a specific report:

![Reports Home](https://docs.speedscale.com/assets/images/screen-shot-2021-08-13-at-11.36.55-am-5820fac14ff1054bd7fb339e6b231590.png)

Click into any report to see more detailed information.

<a id="which-version-ran"></a>

## Which version ran

Every report records the container image the system under test was running, so you can tell which build a replay exercised without asking whoever launched it. At replay start the operator reads the target workload's pod template and records the image, then fills in what the pods actually ran once one is up.

The report list filters and sorts on two tags:

| Tag | Value |
| --- | --- |
| `sutImage` | The primary container's image repository, for example `ghcr.io/acme/orders` |
| `sutImageTag` | The primary container's image tag, or its digest when the reference is pinned by digest alone |

The report itself carries a structured `sutBuild` for the primary container and a `sutContainers` list with one entry per application container in the pod, in pod order. Each entry has the container name, image repository, tag, digest when the reference pins one, and the CPU and memory requests and limits. The primary container's entry also records:

| Field | Value |
| --- | --- |
| `imageDigest` | The registry digest of the image the container actually ran, read from the pod's container status, so two rollouts of a reused tag such as `latest` can be told apart. Empty for an image that was never pulled from a registry, such as one built on the node |
| `podTemplateHash` and `node` | The running pod's template hash and node, read from the first pod on the stamped image |
| `version` | The pod template's `app.kubernetes.io/version` label when set |
| `revision` | The Deployment or Argo Rollout revision annotation when set |
| `replicas` | The replica count the workload asked for |
| `configHash` | A hash over the container's command, args, environment, envFrom sources, volume mounts and their sources, and any `checksum/*` annotation on the pod template. The same image with a different `configHash` is a configuration change. Only the hash is stored, never a value |

The primary container is the first container in the pod that is not a known sidecar. Speedscale's own proxy and the Istio and Linkerd sidecars are recognized by image and container name and left out of `sutContainers`. A Job with an app container and an exporter lists both, with the app container as the primary.

The image tag appears beside the build tag in the report list and on the report page, where hovering it shows the containers, digest, revision, replicas, node and config hash. The report list can be filtered by image tag. From the CLI, `speedctl get report <report-id>` prints `sutBuild` and `sutContainers` with the rest of the report and `speedctl get reports --image-tag <tag>` lists the replays that ran that tag.

Captured traffic carries the same identity. Every RRPair recorded through the sidecar or through nettap is tagged with `sutImage`, `sutImageTag` and, when the pod status reports a registry digest, `sutImageDigest` for the container that served it, so a snapshot says which build it was recorded from and a report says which build it tested. nettap resolves that container from the process on the eBPF path and from the container name the operator injects beside the Java agent, so a pod with several application containers tags each request with the container that served it.

The fields stay empty when there is no pod to read: a replay against a `customURL` target, and a local proxymock replay. Reports and snapshots created before this was added are not backfilled. The `buildTag` on the replay is still yours to set, so you can record a commit hash or pipeline id next to the image the cluster actually ran.

<a id="ai-generated-summary"></a>

## AI-Generated Summary

Each replay report includes an AI-generated summary at the top that highlights the most important findings. The summary provides a plain-language overview of what happened during the replay, calls out key failures or regressions, and suggests where to focus your attention. This is the fastest way to understand replay results without reading through every detail.

<a id="readiness"></a>

## Readiness

The Readiness tab, right after Overview, grades the replay for production readiness: a Ready or Not ready verdict, a letter from A to F for each metric family, a weighted score and a confidence factor.

The test config decides which families block the verdict and at which letter.

See the [Readiness guide](https://docs.speedscale.com/guides/readiness/).

<a id="low-data-mode"></a>

## Low data mode

When a replay runs in [low data mode](https://docs.speedscale.com/reference/glossary/#low-data-mode), a notice above the report tabs says so and explains what is missing.

The generator keeps only a sample of failed requests, so assertions, the error summary, transform issues and recommendations cover only that sample. The responder keeps only totals, so individual mocked calls are not listed. Latency, throughput, request counts and mock counts still cover everything sent.

The Accuracy card on the Overview tab counts responses in this mode, not assertions. On the Readiness tab, the notice names the families that could not see every request or mocked call, so read those letters with care.

To turn the mode off, select **Change in test config** on the notice. The change applies to the next replay.

<a id="llm"></a>

## LLM

A replay that sent streamed LLM requests gets an LLM tab with time to first token, inter-token latency, request latency and token rates, next to the recorded values when the recording had frame timing. See [LLM Streaming Metrics](https://docs.speedscale.com/guides/replay/llm-streaming-metrics/#read-the-results).

<a id="recommendations"></a>

## Recommendations

![Recommendations panel in a replay report](https://docs.speedscale.com/assets/images/report-recommendations-297cc6940aa5eb46c5617f81d2281678.png)

The Recommendations panel surfaces automated insights about issues detected during the replay. Recommendations identify problems like memory growth, unreplaced tokens, latency regressions, error rate deviations, and more — along with suggested actions to fix them. See the [Traffic Recommendations guide](https://docs.speedscale.com/guides/recommendations/) for a full reference of all recommendation types.

<a id="latency-percentiles"></a>

## Latency Percentiles

The performance section includes latency percentile graphs showing P50, P75, P90, P95, and P99 response times. These graphs help you understand the distribution of response times rather than just the average, making it easier to spot tail latency issues that affect a small percentage of requests.

<a id="throughput-timeslice-graphs"></a>

## Throughput Timeslice Graphs

Throughput graphs show request volume over time during the replay, broken into timeslices. Use these to identify whether traffic was evenly distributed or whether there were bursts and gaps that might explain performance anomalies.

<a id="kubernetes-event-overlay"></a>

## Kubernetes Event Overlay

When replaying in a Kubernetes environment, the report can overlay cluster events (pod restarts, OOMKills, scheduling failures) on the performance timeline. This correlation makes it easy to see whether infrastructure issues coincided with performance regressions or errors during replay.

<a id="read-the-outcome-checks"></a>

## Read the outcome checks

The report **Overview** opens with four checks:

| Check | What to inspect |
| --- | --- |
| Completed | Whether the replay completed its execution |
| Accuracy | Whether inbound replay responses matched expectations |
| Mocks | Whether outbound requests matched the configured mocks |
| Goals | Whether configured performance and validation goals passed |

Each check links to the report view that explains it. Completion alone does not prove response correctness. If no goals are configured, a green status does not prove that performance thresholds were checked.

When goals fail, the Overview shows their metric, expected value, and actual value. Use this evidence to distinguish a missed latency or throughput target from a replay setup problem. See [Report Status](https://docs.speedscale.com/guides/reports/status/) and [Performance Details](https://docs.speedscale.com/guides/reports/performance-details/).

<a id="outbound-http-calls"></a>

## Outbound HTTP calls

When the test config has an [`httpOutput`](https://docs.speedscale.com/reference/configuration/assertions/httpoutput/) assertion, the **Accuracy** tab shows **Outbound HTTP calls** next to the Kafka output and [SQL output](https://docs.speedscale.com/reference/configuration/assertions/sqloutput/) results.

A summary says whether the app's outbound calls matched the recording, with the recorded and replayed call counts and how many times the replay ran the recorded tests. If the comparison could not run, an error says why, and a warning appears when the list of differences was truncated.

The table lists each difference with its kind, host, method, endpoint, field, expected and actual values, and how many calls it covers.

<a id="mock-accuracy-by-host"></a>

## Mock accuracy by host

The **Mocked Responses** tab shows a **Mock accuracy by host** table under the Mock Accuracy cards. For each dependency host the app called, it lists the calls the mocks matched, did not match, and passed through to the live service, and the host's accuracy.

Hosts named in an `httpOutput` assertion's `mockRequired` are marked as required. A required host with any unmatched or passthrough calls is marked as not mocked and listed first.

The table appears for reports analyzed after per-host counts were added.

<a id="chaos-rules"></a>

## Chaos rules

When the test config has chaos rules, the **Mocked Responses** tab shows a **Chaos rules** table. For each rule it lists its configured percent and expected share, the requests that matched it while it was active, the responses it perturbed, and how those responses were sent: completed, withheld, reset, partial or write-failed.

With a [`chaosFired`](https://docs.speedscale.com/reference/configuration/assertions/chaosfired/) assertion, the table also shows each rule's allowed fired range and verdict: within band, out of band, not exercised, or required and not exercised. If the rules could not be judged, an error says why.
