starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Multiple checks (for Internet link availability testing) #1529

New issue

Closed

opened 2026-02-28 02:24:19 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 02:24:19 -05:00

Owner

Originally created by @mikolajek-fr on GitHub (Nov 2, 2022).

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

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

Originally created by @mikolajek-fr on GitHub (Nov 2, 2022). ### ⚠️ 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_

deekerman

2026-02-28 02:24:19 -05:00

closed this issue
added the
feature-request

A:monitor
labels

deekerman commented

2026-02-28 02:24:25 -05:00

Author

Owner

@mateuszdrab commented on GitHub (Nov 27, 2022):

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

@mateuszdrab commented on GitHub (Nov 27, 2022): Why not do a ping/DNS check against a highly available DNS server? Google or Cloudflare dns

deekerman commented

2026-02-28 02:24:25 -05:00

Author

Owner

@KarimGeiger commented on GitHub (Jul 19, 2023):

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 commented on GitHub (Jul 19, 2023): 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."

deekerman commented

2026-02-28 02:24:25 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 19, 2023):

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

@CommanderStorm commented on GitHub (Jul 19, 2023): Is this one of the duplicates linked to https://github.com/louislam/uptime-kuma/pull/1236?

deekerman commented

2026-02-28 02:24:25 -05:00

Author

Owner

@KarimGeiger commented on GitHub (Jul 19, 2023):

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

@KarimGeiger commented on GitHub (Jul 19, 2023): Looks like it. Thanks for pointing out that PR, didn't find it earlier myself.

deekerman commented

2026-02-28 02:24:25 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 4, 2023):

@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 commented on GitHub (Dec 4, 2023): @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.

deekerman referenced this issue

2026-02-28 02:33:35 -05:00

Email - Format #1814

deekerman referenced this issue

2026-02-28 02:38:14 -05:00

How long host was down in notification #1949

deekerman referenced this issue

2026-02-28 02:42:47 -05:00

Being able to edit the notification that is being sent out #2090

deekerman referenced this issue

2026-02-28 02:46:41 -05:00

Email Notifications #2208