Table of contents

Check results

If you have API or Browser checks running, you can select them on the main Checkly dashboard and get an overview of the results they have produced so far. To learn about heartbeat check results, visit the Heartbeat checks section

Select a check and you will see a breakdown of its recent runs, together with key availability and performance metrics.

The summary at the top of the page allows for filtering based on the page’s data points and the selected timeframe and locations. Retried check runs do not influence this section; only the final results are considered.

Based on the user’s selection, the metrics in the summary will also be updated to show the most important numbers at a glance. Single tabs in the summary can be clicked to skip to the related section of the page showing a more detailed breakdown of the relevant information.

Check run results can be accessed by selecting them on the time ribbon or by hovering dots and clicking View Details. View Details will open the selected check run in a new browser tab; a simple click on a time ribbon dot will show a preview of the selected check run below it.

Selecting a check execution will take you to the dedicated check result page for it, which will look different based on whether you had been running a Browser or an API check.

When retries are enabled, an additional icon highlights that the check result contains multiple check runs. All attempts as well as the final result are available to view.

The check retries ratio indicates how many of the total checks run were retried due to an initial failed attempt.

If you are using the parallel scheduling strategy, instead of individual locations you will see an aggregated result for all check locations in the time ribbon tooltip. Below the ribbon all locations & their respective status will be displayed as a group. You can select All locations to see an overview of all check runs, or select an individual location to go directly to that check result.

Depending on the type of check, different performance metrics will be shown in the Performance section.

For Browser checks, several performance metrics are shown in separate charts:

1. The total duration of the browser session

2. Load timings for the first page navigation

3. A breakdown of different error types

4. An interactivity summary

5. A visual stability breakdown

For API checks, a detailed response time breakdown is shown:

A performance comparison by location will also be included for both types of check:

The check result page will contain results from multiple locations when using parallel scheduling. Navigate between each location using the sidebar.

Individual browser check results contain:

1. A short check summary, including errors broken down by category.
2. When using Playwright Test Runner you will have an additional section displaying the test steps, error message, and assets (traces, videos, screenshots). Read more about the additonal functionalities of Playwright Test.
3. An error log, only if your script failed.
4. Expandable tabs on page your script navigated to. When expanded, each tab shows its own navigation/loading time ribbon and web vitals… …together with browser console logs, network logs and any screenshots that had been taken (including one screenshot taken automatically on failure).
5. A job log for the check.

API check results will expose key performance and correctness data about the HTTP response received from the target endpoint.

These include:

1. The request performed

2. Any assertions that were included in the check

3. All data related to the request and its response, such as

   a. Response body

   b. Request & response headers

   c. Query params

   d. Check job log

4. Timings, such as

   a. Wait

   b. DNS

   c. TCP

   d. First Byte

   e. Download

When checks are retried, a dropdown will indicate that the check result contains multiple check runs:

1. The initial failed attempt
2. The final result (which may have failed or succeeded)

When selecting a check run, all data and assets are available for inspection for each attempt.

How we run checks Global locations & scheduling strategies

You can contribute to this documentation by editing this page on Github