sam/dev_arc_aws
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add temporary debug logging to Uptime Kuma listResources

Browse source 
Diagnosing why a connected Uptime Kuma instance with real monitors is
producing zero Resources — logs monitor count, active flags, and last
heartbeat per monitor so we can see exactly what the Socket.IO session
returns.
This commit is contained in:
Claude 2026-06-21 12:16:44 +00:00
parent 58f007e6db
commit 89dd3471db
No known key found for this signature in database
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
backend/src/integrations/uptimeKuma.ts
View file

@ -94,6 +94,11 @@ export const uptimeKuma: IntegrationAdapter = {
// single "done" signal, so give it a short window to arrive. // single "done" signal, so give it a short window to arrive.
await new Promise((resolve) => setTimeout(resolve, 2500)) await new Promise((resolve) => setTimeout(resolve, 2500))
console.log(`[uptimeKuma] received ${monitors.size} monitor(s), ${lastHeartbeat.size} heartbeat(s)`)
for (const m of monitors.values()) {
console.log(`[uptimeKuma] monitor ${m.id} "${m.name}" active=${m.active} heartbeat=${JSON.stringify(lastHeartbeat.get(m.id))}`)
}
const resources: Resource[] = [] const resources: Resource[] = []
for (const monitor of monitors.values()) { for (const monitor of monitors.values()) {
if (!monitor.active) continue if (!monitor.active) continue