Estate watchdog · K3s infrastructure
Trinity
watchdog.
What is running, when it last checked in, and what failed. Generated at 2026-11-19 10:44; refresh the page for a new check. This is not a screenshot and nothing here is hardcoded.
Current state
Trinity is healthy.
Ready · CPU 30.1% · RAM 60.8% · in this state since 2026-11-17 00:58.
Watchdog itself
- Collection interval
- Every minute
- Stale after
- 10 minutes
- Last check
- 2026-11-19 10:42 (79s ago)
- Next check
- within one minute
- Kind
- k8s_node
- Group
- K3s infrastructure
Schedule
When it last ran and when it runs next
- Schedule
- Event driven - no fixed schedule
- Previous run
- 2026-11-19 10:42 - OK (-)
- Next run
- Next run unknown. The scheduler has not published it.
- Last successful run
- 2026-11-19 10:42 (79s ago)
- Heartbeat
- 79s ago
- Tracking since
- 2026-11-12 10:23 (7 days)
- Longest gap, 24 h
- 5m
Weekly progress
Has this been working all week?
Success rate, 7 days: 37% across 5856 checks.
- 2% Fri
- 14% Sat
- 23% Sun
- 100% Mon
- 100% Tue
- 100% Wed
- 100% Thu
Each tile is one local day: green means at least 90% of checks succeeded, amber 50-89%, red below 50%, grey no attempt. Health is measured from recorded runs, not from a process check, so a frozen worker shows as failed or missing.
Checks
Evidence behind the state
| Check | State | Evidence |
|---|---|---|
| Monitor evidence freshness | pass | last check 79s ago; stale after 5 minutes |
Recent runs
Last terminal runs
| Started | Duration | Trigger | Status | Work done | Error |
|---|---|---|---|---|---|
| 2026-11-19 10:42 | - | schedule | OK | Ready · CPU 30.1% · RAM 60.8% | — |
| 2026-11-19 10:37 | - | schedule | OK | Ready · CPU 30.7% · RAM 60.0% | — |
| 2026-11-19 10:32 | - | schedule | OK | Ready · CPU 37.1% · RAM 60.2% | — |
| 2026-11-19 10:27 | - | schedule | OK | Ready · CPU 30.7% · RAM 61.8% | — |
| 2026-11-19 10:22 | - | schedule | OK | Ready · CPU 32.8% · RAM 62.7% | — |
| 2026-11-19 10:17 | - | schedule | OK | Ready · CPU 33.0% · RAM 60.6% | — |
| 2026-11-19 10:12 | - | schedule | OK | Ready · CPU 31.0% · RAM 60.4% | — |
| 2026-11-19 10:07 | - | schedule | OK | Ready · CPU 27.3% · RAM 61.1% | — |
| 2026-11-19 10:02 | - | schedule | OK | Ready · CPU 33.7% · RAM 68.6% | — |
| 2026-11-19 09:57 | - | schedule | OK | Ready · CPU 26.7% · RAM 71.6% | — |
Uptime
Measured availability
- 24 hours
- 100.0%
- 7 days
- 32.9%
- 30 days
- 32.8%
- 24 h samples
- 288
Uptime is the share of recorded checks that passed. Gaps reduce coverage; they are never assumed up.
Recent failures
Last 20 incidents
| Started | Duration | Severity | Summary | Resolution |
|---|---|---|---|---|
| 2026-11-15 22:33 | 3m | warning | unavailable | 2026-11-15 22:36 |
| 2026-11-15 20:27 | 15m | warning | unavailable | 2026-11-15 20:42 |
| 2026-11-15 19:50 | 5m | warning | unavailable | 2026-11-15 19:55 |
| 2026-11-15 18:36 | 23m | warning | unavailable | 2026-11-15 18:59 |
| 2026-11-15 17:55 | 39m | warning | unavailable | 2026-11-15 18:34 |
| 2026-11-15 17:37 | 4m | warning | unavailable | 2026-11-15 17:41 |
| 2026-11-15 17:17 | 3m | warning | unavailable | 2026-11-15 17:20 |
| 2026-11-15 15:55 | 79m | warning | unavailable | 2026-11-15 17:15 |
| 2026-11-15 15:12 | 42m | warning | unavailable | 2026-11-15 15:53 |
| 2026-11-15 14:02 | 68m | warning | unavailable | 2026-11-15 15:10 |
What this covers
Scope and honesty
Covers the checks shown above. Does not cover behaviour the monitor cannot observe.
A 200 from a landing page proves reachability, not a working product. Missing data is shown as unknown, never as zero or green. Alerts and silences are evaluated by the same monitor that renders this page.