7.9Reading the results

In the dashboard#

1. Open the monitor and find Recent checks.
2. To see only problems, select Failed only. Select All to see every check.
3. Each row shows the status, then the error message or a summary such as 200 · <region> · 6 steps. It also shows the response time and how long ago the check ran.
4. Select a row with an arrow to open it.

An open check shows one line per step. Each line has ✓ (passed) or ✗ (failed), the step name, a bar that compares its time with the slowest step, and its time in ms. Below the steps you see the first error and the screenshot, or a line that starts with "No screenshot:" (see 7.10).

Step numbers start at 0#

The editor numbers steps from 1. Result messages and the step list in a result count from 0.

So the message step 2 (click): … is about row 3 in the editor. Add 1 to find the row.

The row's main message is the first error of the check, such as step 2 (click): …. For the meaning of each message, see the tables in 7.4, 7.7 and 7.8.

Through the API#

ListExecutions returns the results (see 13.8). For a browser check:

• statusCode is the HTTP status of the first page, when it is known.
• responseTimeMs is the time the whole script took.
• errorMessage is the failure message.
• metadataJson holds steps, a list of {kind, ok, ms, error}. Like the dashboard, the list starts at 0. error appears only on a failed step.
• metadataJson also holds screenshot when one was kept, or screenshot_skipped with the reason.