uptime-kuma icon indicating copy to clipboard operation
uptime-kuma copied to clipboard

Multiple checks (for Internet link availability testing)

Open mikolajek-fr opened this issue 2 years ago • 1 comments

⚠️ Please verify that this feature request has NOT been suggested before.

  • [X] I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

I have a monitor on an external service to check Internet link availability. If this service is down, my monitor is down but maybe it's just this external service, not my Internet link.

✔️ Solution

It could be nice to have a monitor with multiple checks, for example : google.com AND amazon.com AND apple.com. Less than 3/3 down : monitor is still up, 3/3 down : monitor is down.

❓ Alternatives

Can be a special monitor which checks some others monitors (one monitor for external service 1, one monitor for external service 2, one monitor for external service 3, one last monitor for these 3 monitors).

📝 Additional Context

No response

mikolajek-fr avatar Nov 02 '22 07:11 mikolajek-fr

Why not do a ping/DNS check against a highly available DNS server? Google or Cloudflare dns

mateuszdrab avatar Nov 27 '22 23:11 mateuszdrab

I too would love to see a way to detect false-positives. Sometimes, my uptime kuma instance seems to go offline due to the hosting provider having network issues, resulting in all monitors going down. Once it comes back online, I get spammed with alerts regarding the downtime as each service "comes back online", while in reality uptime kuma was the service being down. Therefore, having an option to say "if 1.1.1.1 and 8.8.8.8 fail to ping, consider yourself down and don't bother changing monitor states."

KarimGeiger avatar Jul 19 '23 11:07 KarimGeiger

Is this one of the duplicates linked to https://github.com/louislam/uptime-kuma/pull/1236?

CommanderStorm avatar Jul 19 '23 16:07 CommanderStorm

Looks like it. Thanks for pointing out that PR, didn't find it earlier myself.

KarimGeiger avatar Jul 19 '23 16:07 KarimGeiger

@mikolajek-fr We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #1236 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) ⇒ I am going to close this as a duplicate.

CommanderStorm avatar Dec 04 '23 20:12 CommanderStorm