Monitoring

Coverage

Monitoring coverage tracks how much of each API spec is actually monitored — the share of a spec's endpoints that have a monitor. As your API grows, coverage keeps the question "did we forget to monitor the new endpoints?" answered automatically.

The Spec Coverage card

The Spec Coverage card on the Health Dashboard shows one row per spec in the project:

  • The count and percentage — e.g. 12/18 endpoints (67%).
  • A progress bar, color-coded: green above 80%, amber from 50–80%, red below 50%.
  • A status line: Fully covered at 100%, otherwise how many endpoints are not monitored.
  • A Generate Missing button (requires monitoring:write) that opens the Generate-from-Spec wizard to fill the gaps — endpoints that already have a monitor are marked and skipped, so re-running it never duplicates anything.
The Spec Coverage card with progress bars and Generate Missing

Coverage hints

When a spec has unmonitored endpoints, the dashboard also shows a hint banner above the charts: "N endpoints in <spec> have no monitor." with a Set up monitoring shortcut into the wizard. You can dismiss a hint — it stays hidden until the number of missing endpoints changes, then reappears so genuinely new gaps don't go unnoticed.

Keeping coverage up as you publish

Coverage is only useful if it keeps pace with your spec. Under Monitoring → Settings, the Spec publishing section controls what happens when a new spec version is published:

  • Auto-create monitors for new endpoints on — Routebase automatically creates a monitor for each endpoint that isn't monitored yet, in the production environment and pinned to the published version.
  • Off (default) — you get a notification about new unmonitored endpoints instead, and decide yourself via Generate Missing.

What counts as covered

An endpoint counts as monitored when a monitor is linked to it — which is what Generate from Spec, the API Designer's Create Monitor context action, and Watch for drift produce. A hand-created monitor pointed at the same URL, but without the endpoint link, doesn't count toward coverage (and can't do schema validation either), so prefer the linked paths.

The fastest of the three is Watch for drift: one dialog covers a whole spec in one environment, endpoint-linked and with validation already on, and re-running it only fills the gaps. It sits in the API Designer's toolbar ⋯ menu and in the empty state of Monitoring → Contract Drift — see Contract Drift. Coverage and drift watching are not the same measure, though: coverage asks how many endpoints have a monitor, the Contract Drift page asks how many of those monitors could actually validate a response.