Results
Every time a monitor runs, APIContext records a result — a complete snapshot of the request, the response, and the verdict. Results are the raw data that powers dashboards, quality scores, and conformance analysis.
What a result contains
Each result stores:
| Field | Description |
|---|---|
| Pass/Fail/Warning verdict | Determined by the monitor's conditions and assertions |
| HTTP status code | The status code returned by the API |
| Latency breakdown | DNS lookup, TCP connect, TLS handshake, server processing time, data transfer, and total time |
| Trigger reason | Why the call was made — manual run, scheduled event, or another trigger |
| Node location | Which global test node executed the call |
| Request sent | The full HTTP request including method, URL, headers, and body |
| Response received | The full HTTP response including headers and body |
| Variables | Any environment or workflow variables that were set during the call |
Where to find results
Results appear in three places:
- Monitor Results tab — every execution of a single monitor, with drill-down to full request/response detail
- All Call Results (under Investigate) — a project-wide view of every request across all monitors, filterable by result category, location, and time range
- Project Overview — an aggregated summary row per monitor showing Quality Score, availability percentage, slow percentage, and average latency
Why the latency breakdown matters
The breakdown into DNS, TCP, TLS, processing, and transfer segments lets you isolate whether a performance problem originates at the network layer, the CDN, or the application itself. This feeds into APIContext's network monitoring capabilities.
See also
- Understanding the results — how to navigate and interpret the results UI
- CASC Score — how results feed into the quality score
- Network monitoring — using latency breakdowns to diagnose network-layer issues