Documentation

Sometimes a monitor’s history stops being useful: you pointed it at a staging URL for a week, a misconfiguration produced a wall of false downtime, or you are reusing an existing monitor for a brand-new service. Deleting and recreating the monitor loses its ID, alert wiring and probe assignments. Reset Statistics is the middle ground — it wipes the accumulated data and starts the timeline from zero while keeping the monitor itself intact.

This action is irreversible. There is no undo and no backup of the wiped rows.

Where to Find It

The control lives in the monitor edit form, not on the monitor detail page:

1. Open the monitor and click Edit (or the pencil icon).
2. Expand Advanced Options at the bottom of the form.
3. Click the red Reset statistics button.
4. A confirmation dialog asks you to type the monitor’s name before the button activates.

The button only appears when editing an existing monitor — never while creating one.

What Gets Wiped

After the reset, the monitor keeps running on its normal schedule — the very next check starts a fresh timeline.

Confirmation & Safety

Resetting statistics is gated by two layers so it can never fire by accident:

• Type-to-confirm in the UI — you must type the exact monitor name; the confirm button stays disabled until it matches.
• Explicit flag in the API — the request must carry confirm: true, otherwise it is rejected with 422 Unprocessable Entity. This protects against accidental shell or LLM-tool invocations.

Only one reset can run per monitor at a time. If a reset is already in progress, a second attempt returns 409 Conflict — wait a moment and retry.

Large Monitors

For monitors with millions of stored checks the wipe is batched on the server and can take up to a few minutes. The UI shows a Resetting… state and waits up to 180 seconds for the operation to finish, then reports how many checks, ranges and incidents were removed. The monitor’s status badge, in-flight state and cached SSL info are refreshed automatically once the reset completes.

API & MCP

The same operation is available outside the UI:

• REST: POST /api/v1/monitors/:id/reset-stats with body { "confirm": true }. See the API Reference → for authentication and the response summary.
• MCP: the reset_monitor_stats tool exposes the same action to AI clients (it is annotated destructive and also requires confirmation).