From 89dd3471db7cc67c5d7490f224134a9a5eee35d6 Mon Sep 17 00:00:00 2001 From: Claude Date: Sun, 21 Jun 2026 12:16:44 +0000 Subject: [PATCH] Add temporary debug logging to Uptime Kuma listResources MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- backend/src/integrations/uptimeKuma.ts | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/backend/src/integrations/uptimeKuma.ts b/backend/src/integrations/uptimeKuma.ts index 496b845..eaefe47 100644 --- a/backend/src/integrations/uptimeKuma.ts +++ b/backend/src/integrations/uptimeKuma.ts @@ -94,6 +94,11 @@ export const uptimeKuma: IntegrationAdapter = { // single "done" signal, so give it a short window to arrive. 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[] = [] for (const monitor of monitors.values()) { if (!monitor.active) continue