Pause a check

Unique check identifier.

Human-readable name.

Stable project-scoped identifier (may be empty string if not set).

on_demand means the check has no cadence: it never arms an absence deadline, so silence between runs never alerts. Run-scoped detection (max_runtime_s, step_timeout_s) still applies once a run starts, and expect_every_s — the silence floor — is the only way to detect absence between runs.

Period in seconds (only meaningful for schedule_kind=simple).

Cron expression (only present when schedule_kind=cron).

IANA timezone.

Grace period in seconds — the silence tolerance and the first-run deadline, and the overrun budget when max_runtime_s is unset.

Run-duration budget in seconds for the overrun deadline only. Omitted from the response when unset, in which case the overrun rule falls back to grace_s. Never set on http monitors.

Progress budget in seconds for the stall rule. Omitted from the response when unset, in which case stall detection is disabled. Never set on http monitors.

Silence floor in seconds. Omitted from the response when unset, in which case absence is detected only by the schedule — and, for an on_demand monitor, not at all between runs.

Notification duration floor in seconds. Omitted from the response when unset, in which case every info-class notification (success, started, every-run, note) fires regardless of how short the run was. Never set on http monitors. Never suppresses down, fail, recovery or blocked.

How long (in seconds) the check may sit blocked before a blocked incident opens. Omitted from the response when unset — that does NOT mean the check waits forever, it means the 24-hour default applies.

Consecutive explicit failures required before an incident opens (fail cause only). Always present; 1 means "open on the first failure", the default.

RFC 3339 timestamp from which deadlines are computed.

Current check status derived from ping history.

RFC 3339 timestamp of the most recent ping received.

RFC 3339 timestamp when the next ping is expected.

RFC 3339 timestamp after which an alert is sent if no ping arrives.

When true the check does not alert regardless of ping status.

RFC 3339 timestamp until which the check is snoozed. Alerts are suppressed while this is in the future; null or absent when the check is not snoozed.

RFC 3339 UTC timestamp when the check was created.

The URL your service should HTTP-GET to record a successful ping.

Monitor mode. Omitted on responses when the value is the default heartbeat.

URL being probed (HTTP monitors only; omitted otherwise).

HTTP method used for the probe (HTTP monitors only; omitted otherwise).

Expected response body substring (HTTP monitors only; omitted otherwise).

Probe interval in seconds (HTTP monitors only; omitted otherwise).

Expected HTTP status code (HTTP monitors only; omitted otherwise).

Probe timeout in seconds (HTTP monitors only; omitted otherwise).

Whether the probe follows redirects (HTTP monitors only; omitted otherwise).

RFC 3339 UTC timestamp when the next probe is scheduled (HTTP monitors only; omitted otherwise).

CI provider bound to this check (omitted when no CI binding is set).

True when a CI binding is set on this check (omitted when false).

Webhook URL for this CI check (omitted when no CI binding is set). POST this URL from your CI provider with the ci_secret as the HMAC secret.

WRITE-ONCE — returned ONLY in the 201 create response and the POST /api/v1/checks/{id}/ci/regenerate response. NEVER returned on GET or list. Copy it immediately; it cannot be retrieved again (use regenerate to rotate).

Optional workflow/job name filter narrowing which CI runs this check watches (omitted when unset, which watches every workflow).

Optional branch filter narrowing which CI runs this check watches (omitted when unset, which watches every branch).

Maximum pings allowed in a rolling 1-hour window. Exceeding it opens a runaway-cause incident, which detects a looping agent or job pinging abnormally fast. Omitted from the response when disabled for this monitor.

Id of the agent that owns this monitor. Omitted/null when the monitor is unattached — including right after its owning agent was deleted: DELETE /api/v1/agents/{id} unowns the monitors it owned, it does not delete them.

The scanner that discovered this monitor (crontab, github-actions, k8s-cronjob, systemd-timer). Omitted when a human created the monitor, which is the state of every monitor that predates discovery — and such a monitor is never reconciled, so a scan can neither adopt nor delete it.

The stable path within source_kind that identifies exactly what was found. Together with source_kind and the project it is the discovery reconcile key.

source_kind and source_ref are always either both present or both omitted: a half-set identity is never stored.

What this monitor's traces keep of prompt, command and tool content. dropped (the default) removes the content attributes (prompts, completions, commands, tool arguments, results and definitions, retrieved documents, working directories) of every recognised vocabulary entirely; lengths such as user_prompt_length, token counts and cost are kept. Error text (error, error.message, exception.message, exception.stacktrace and the span's status message) is kept at dropped, redacted and then cut to 512 characters, and a cut marks the span or log event truncated. redacted opts in to storing that content, with every secret-shaped value replaced by [REDACTED:<class>] at ingest, before anything is queued or stored: API keys (LastPing, Anthropic, OpenAI, GitHub, GitLab, npm, AWS access key ids, Slack, Stripe, Google, Hugging Face, Perplexity, Fireworks, Supabase, New Relic, Airtable, Terraform Cloud, Firebase), HashiCorp Vault tokens, age secret keys, Discord bot tokens, Slack, Discord and Teams webhook URLs, Authorization header values, JWTs, private key blocks, password=/token=/api_key= style assignments (subscripted ones such as os.environ["API_KEY"] = ... and Dockerfile ENV/ARG lines included), SQL PASSWORD '...' and IDENTIFIED BY clauses, the Redis AUTH command, .netrc passwords, command-line password flags and the argument after them (any secret-named --flag, -p after a login subcommand, redis-cli -a), cookies, credentials in URLs, the value of any attribute or JSON field whose name is secret-named (password, token, api_key, secret, the same word in several other languages, an Authorization or X-Api-Key header and the like; Idempotency-Key and request, correlation and trace ids are not secrets), including JSON carried inside another JSON string such as tool-call arguments, and long high-entropy tokens. A bytes attribute that is valid UTF-8 is scanned and stored as its text. A span that had a value redacted carries lastping.redacted_values. A request whose redaction work exceeds a fixed budget stores [REDACTED:over_budget] for the values it could not scan, never the values themselves. In both modes every remaining value is redacted the same way. There is no setting that stores content unredacted. A change reaches ingest within 60 seconds: ingest caches each monitor's setting for up to a minute, so an export sent just after the change may still be handled the old way.

Always present.

The console's four-way grouping of this monitor, derived server-side so every surface groups it the same way. agent wins over the rest: an agent's heartbeat is the agent's. A CI monitor is one with a ci_provider, not one with monitor_type: "ci" — nothing in the product writes that value.

Uptime over the last 90 days, or since the monitor was created if that is more recent, as a percentage with two decimals. For an HTTP monitor this is the share of probes that succeeded; for every other type it is derived from incident downtime over the window. Null when an HTTP monitor has no probe history yet, and null for any other monitor that has never been pinged. A monitor created three days ago reports on those three days, not on 90 days of assumed success, so the window varies per monitor and the console says so beside the figure.

The most recent probe's latency. HTTP monitors only; null for every other type and for an HTTP monitor with no probe yet.

How many distinct alert destinations would hear about this monitor FAILING: the destinations routed on down, fail, blocked or every-run. Distinct destinations, not route rows, so one destination routed on both down and fail is one place the alerts go. every-run counts because it fires for every completed run, a failed one included. A route on recovery, success, started or note is not counted: routes are resolved per event with no fallback, and none of those four ever fires for a failure, so a monitor routed only on them has nowhere for its bad news to go. 0 means failures would be silent, which the console flags as "Not routed" and Home counts in overview.alerts.monitors_unrouted.

Version of the Claude Code hook script last seen on a start ping; null when no hook that reports a version has sent a start. Older than hook_version_current means re-run set-up.

The hook script version set-up installs today. Compare it with hook_version.

When hook_version was last recorded, from a start ping. Refreshed at most once an hour while the version is unchanged. Null when no hook that reports a version has sent a start.

Latest time this monitor received a Claude Code run (a hook start that reported a version, or a trace whose source is Claude Code). With hook_version null and a recent value here, the machine runs an older hook or none.