id, severity, observed, threshold,
findings, suggestedAction — so a script can treat them all the same way.
healthchecks list
List every healthcheck the platform exposes, including ones that are defined but not yet implemented on the backend. Not-yet-implemented entries carry anotImplementedReason you
can surface to users.
Run
healthchecks list for the live set rather than trusting this table — it is the
authority, and it grows.
healthchecks run
Run a single check by ID, or--all to run every implemented check in parallel and
aggregate the results.
6 — the check ran, and
something is unhealthy. That is a failing gate rather than an error to retry:
healthchecks vs. detections healthcheck
detections healthcheck is
detection-specific and can run the configs before validating them. healthchecks run
covers the whole pipeline — reviewing, takedowns, and assets as well — through the public
healthchecks API.
Related
- Healthcheck endpoints
queues snapshotfor the raw queue counts behind several checks