Kuma server-side link status monitoring

[jaclas]

⚠️ Please verify that this bug has NOT been raised before.

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

I have Kuma installed on my home server, it monitors many external servers where my applications are running. Unfortunately, my home connection is unreliable and often Kuma signals problems with no response from the configured servers, but not because they are offline, but that offline is the Kuma server.

Is it possible to solve this somehow? Can Kuma check the status of the global connection, e.g. by pinging to the DNS servers?

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.2

💻 Operating System and Arch

Ubuntu 22.04

🌐 Browser

Chrome

🐋 Docker Version

20.10.14

🟩 NodeJS Version

No response

[mabed-fr]

Hello, You are experiencing the concerns of many people. One of the solutions that can help you out will be the implementation of:

#1236

You create a "parent" monitor (ping google) and if this monitor is down the other services will not be defined as down

[jaclas]

Thx, but why is this hanging around so long and not merged? This is a very useful feature, I don't understand why there is resistance to implementing it.

[CommanderStorm]

See #2693 (comment) for further context

Said feature would need a heavy rebase to make it shippable.
It for example does not use the new monitor syntax (not piling everything into monitor.js) or the new db-independent migrations.

[github-actions]

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

[github-actions]

This issue was closed because it has been stalled for 2 days with no activity.