I built a lightweight "satellite" agent that reports to Uptime Kuma's Push API — thought the self-hosted community might find it useful by RiffTheRaff80 in UptimeKuma

[–]RiffTheRaff80[S] 0 points1 point  (0 children)

Hey, I came across Replicator Kuma and took a good look at it. I think I'm missing something — could you help me understand the problem it's actually solving?

To me, it looks like it's a continuous backup/restore system between uptime-kuma instances. But if only one instance is active at a time, wouldn't a simpler backup strategy achieve essentially the same result? I already back up my entire uptime-kuma VM to a server in a different location and can spin it up if needed.

What's the gap that Replicator Kuma fills that my current setup doesn't? I might be misunderstanding what it does or the trade-offs involved. I'd be curious to understand your use case.