Command Info

Name: cronmanager:check-heartbeats

Description: Alert on fleet servers whose CronManager heartbeat is stale

Status: completed

Start Time: 2026-09-30 04:15:02

End Time: 2026-09-30 04:15:02

Total Time: 0 seconds

Dispatched Jobs Count: 0

Successful Jobs Count: 0

Failed Jobs Count: 0

Output

04:15:02 Lock acquired for command: cronmanager:check-heartbeats
04:15:02 🔍 Checking CronManager heartbeats (stale after 36h)
04:15:02 ⏭️ kamaterajc — unresolved alert already active, message refreshed
04:15:02 ⏭️ ns3018201 — unresolved alert already active, message refreshed
04:15:02 ⏭️ ns3022760 — unresolved alert already active, message refreshed
04:15:02 🔍 Unmatched hostnames (no RunCloud server mapping):
04:15:02 • ns3018201
04:15:02 • ns3022760
04:15:02 🗑️ Purged decommissioned heartbeat: kamaterajc (KamateraJC, last report 355h ago)
04:15:02 📊 Heartbeat check summary:
04:15:02 Stale heartbeats: 3
04:15:02 Alerts created: 0
04:15:02 Decommissioned heartbeats purged: 1
04:15:02 Orphaned alerts resolved: 0
04:15:02 Lock released for cronmanager:check-heartbeats