mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Only down if ALL monitors are down #3410
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3410
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tebwritescode on GitHub (Jun 14, 2024).
📑 I have found these related issues/pull requests
None found
🏷️ Feature Request Type
Change to existing monitor
🔖 Feature description
There is currently a way to group multiple monitors and consider the group to be down, if any of the monitors in the group go down. It would be nice if there was an option to change this between ANY and ALL. That way only if all of the monitors in the group go down a notification is sent that the group is down.
✔️ Solution
Lets take a docker container in my homelab for example. I currently run Uptime Kuma on a remote server. The two servers communicate through tailscale mostly. There have been some instances where tailscale goes down and notifications are sent that all my docker containers are down. If I was able to add the tailscale address, a remote push, an external IP address, and the DNS address of the monitored container, I would no longer have to chose which connection is the most reliable. If tailscale goes down, but the DNS still works, Uptime Kuma knows that the monitor is depreciated but still online.
❓ Alternatives
I have not found any alternate route of doing this.
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jun 14, 2024):
Duplicate of #3387