Reading the dashboard#

The Dashboard is a grid: your checks down the side, your monitors across the top, and each cell showing whether that check passed the last time that monitor ran it. It refreshes on its own every 30 seconds.

Layouts#

Use the view switcher at the top of the page to change how monitors are grouped:

• Collapsed (the default) — every monitor merged into a single column per check, so you see an up/down count rather than a wall of cells. Good for a quick glance across a lot of checks.
• Grid — one column per monitor, so you can see exactly which monitor is reporting a failure.
• By class — splits your own monitors from the shared fleet into two groups, useful once you’re using both.

Your choice is remembered in the page’s own link as you navigate, so paging or filtering won’t silently reset it back to the default.

Status page#

The Status page reuses the same grid, filtered down to only the checks currently failing somewhere — it’s the “what’s on fire right now” view, and it uses the exact same definition of “failing” as the Dashboard, so the two never disagree.

Drilling into a check#

Click any check’s name to open its detail page:

• A response-time chart, with a range picker (1h up to all-time).
• An uptime table, and a list of recent individual results.
• If the check runs on more than one monitor, you can filter either view down to just one.

What’s next#

You now have the core loop: a monitor running, a check watching something, and a place to see the result. From here, the Guides section covers notification channels (so you find out about a failure without having to watch the dashboard), the full set of check-matching options, and managing monitors day to day.