0% 5h quota used ·
resets in 2h
live · 08/09/2026 12:04 CEST
The daemon watching itself
Heartbeats, alert state, locks and boots, as the health tick last recorded them.
Daemon
live
pid 1 · up 23m
Last tick
35s ago
08/09/2026 12:04
Alerts held
0
per-key failure state
Spent today
$53.34
$53.34ceiling $540
Pollers
a loop silent for three times its interval counts as stalled| Loop | Every | Last run | Silent for | Last error | |
|---|---|---|---|---|---|
| approvals | 300s | 08/09/2026 12:00 | 4m | none | ticking |
| triggers | 300s | 08/09/2026 12:00 | 4m | none | ticking |
| queue | 30s | 08/09/2026 12:04 | 3.1s | none | ticking |
| chat | 60s | 08/09/2026 12:03 | 1m | none | ticking |
| cli-version | 86400s | 08/09/2026 11:40 | 23m | none | ticking |
| balances | 3600s | 08/09/2026 12:00 | 4m | none | ticking |
No alert state on file — nothing has failed often enough to be tracked.
Locks
one per task; a lock older than the task budget plus fifteen minutes is stale and gets stolenNo locks held — nothing is running right now.
Boots
four in ten minutes is a crash loop- 08/09/2026 11:40 24m ago
What this page cannot see: the container or the host being gone. Every check above runs inside the process it is checking, so a dead daemon shows up here only as a health file that stopped moving — and if this console is reading a stale copy of the directory, not even that. Closing that gap needs a watcher outside the box.