# The dashboard, explained

The **Sites** dashboard (`/sites`) is where all your monitors live. Each row shows a monitor's current
state, recent uptime, and key metrics at a glance.

## Reading a row

- **Status** - up (green), down (red), paused or in maintenance, with a recent-history strip covering **6
  hours / 24 hours / 7 days** (shown in the Full view's status column header).
- **Uptime** - the percentage over the selected window, computed as up time divided by (total time minus
  time in maintenance) - a monitor in a maintenance window counts as neither up nor down against the
  percentage.
- **Metrics** - response time, HTTP status, certificate expiry, IP address, connection time and more,
  depending on the monitor type.

Down monitors float to the top of every view so problems are visible first, unless you explicitly sort by
another column.

## Views

Switch between **Full**, **Card**, **Grouped**, **Simple** and **Tall** layouts to suit how many monitors you
have and how much detail you want per row.

## Actions

Open a monitor to see its [results and incidents](/monitors/down-detection/), edit its settings, or select
several and use **bulk edit** to change locations, tags, alert contacts or pause state on many monitors at
once.

## Do it with the API

The dashboard's own data comes from `GET /monitor` with `expand=settings,attached,lastResult,lastIncident,count`
(add `groupBy` and a time window to `GET /monitor/result/summary` for uptime figures). An MCP client uses
`list_monitors` for the roster and `get_uptime_summary` for the uptime/response-time figures behind the
percentage column.

## Related

- [What a monitor is](/monitors/what-a-monitor-is/)
- [How down detection works](/monitors/down-detection/)
- [The account-wide uptime report](/reports/uptime-reports/)