# Monitoring CI

Where to see what runs, what waits and why, how your runners and pools are doing, and what CI used.

## Runs

- **Runs** under CI lists the runs of every repository, with counts by status and filters for
  **Status** and **Trigger**. It needs `ci:ListRuns` on `rn:ews::<organization id>:ci:*`.
- A repository's **CI** tab lists its runs by workflow, with filters for workflow, event, status,
  branch and actor; `dcloud ci runs list` gives its 50 newest.
- A queued run says why it waits; a failed run says why it failed (see [Watch a run](watch-a-run.md)).

## Runners and pools

**Runners** under CI shows each runner's status (**Idle**, **Busy**, **Offline** once it has not
reported for five minutes, **Disabled**), its machine, its current or last run and when it was last
seen; the list refreshes every 15 seconds. `GET /ci/api/runners` gives the same, with `presence`,
`currentRun` and `lastRun`.

Under **Runner pools**, the **Scaling** column shows how many machines each pool wants now, and its
tooltip the last decision, such as "2 running + 3 waiting + 1 spare → 6 (min 0, max 10)".
`dcloud ci runner-pools get` adds the jobs waiting and running and each machine.

## Usage

Usage records CI under three meters: **Job minutes** on platform machines, **Self-hosted runner
minutes** (recorded at €0), and **Logs, artifacts and caches** stored, measured daily. A runner
pool's machines appear as instances.

## Audit

Writes, every log and artifact read (allowed or refused), and every OIDC token are in the audit log
(see
[Security in CI](security.md)).

## Related

- [Watch a run](watch-a-run.md)
- [Troubleshooting](troubleshooting.md)
