This board covers the staging install of Slatepipe that backs the run-history demo. It watches the parts of Slatepipe itself - not the pipelines being recorded, which live on the run history.
slatepipe-collector
Operational
ingest :7180
99.98%
Read-only interface
Operational
:7181, bound to localhost
99.95%
PostgreSQL store
Operational
runs · steps · events
99.99%
Agent reporting
Operational
wrapped-command fleet
99.90%
Alert delivery
Operational
SMTP or webhook
99.97%
Documentation & downloads
Operational
this site
100.00%
Ninety days, one cell per day■ operational■ degraded■ outage
Bars are drawn from /api/status.json at load; the uptime figures are the ninety-day rolling numbers.
Get a note when something breaks
One mail per incident, plus the all-clear. No digest, no marketing - there is nobody here to write one.
Recent incidents
- Alert emails delayed about six minutes9 Oct 2026 · resolved · alert delivery
- Nightly prune held the runs-table lock20 Sep 2026 · resolved · collector, interface
- Run detail loaded the error tail twice2 Sep 2026 · resolved · interface
Looking for the pipeline numbers rather than Slatepipe's own health? The run history is the week of nightly jobs behind the screenshots, and what this will not do is the shortest way to rule us out.