High Availability deployments with shared resources and alerts #2189

Open
opened 2026-02-28 02:45:59 -05:00 by deekerman · 1 comment
Owner

Originally created by @zszen on GitHub (May 15, 2023).

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

  • I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I hope Uptime-Kuma supports high availability deployment solutions, so that when a node of Uptime fails, the alert system does not cause paralysis. When multiple Uptimes are running, alerts only notify once, not multiple times. They share a database and settings.

✔️ Solution

Unclear how to implement

Alternatives

No response

📝 Additional Context

No response

Originally created by @zszen on GitHub (May 15, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description I hope Uptime-Kuma supports high availability deployment solutions, so that when a node of Uptime fails, the alert system does not cause paralysis. When multiple Uptimes are running, alerts only notify once, not multiple times. They share a database and settings. ### ✔️ Solution Unclear how to implement ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_
Author
Owner

@ScrumpyJack commented on GitHub (May 16, 2023):

Similar to https://github.com/louislam/uptime-kuma/issues/3124

@ScrumpyJack commented on GitHub (May 16, 2023): Similar to https://github.com/louislam/uptime-kuma/issues/3124
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2189
No description provided.