mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Distributed Monitoring #2160
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#2160
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 @elimelamed on GitHub (May 4, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
Separate the monitoring engine and the database / ui into different containers
providing central server (act as the main db + UI) to connect multiple monitor agents (a.k.a. Probs) that perform the actual monitoring and send the data to the central application
this will allow scale and monitoring of isolated networks in different locations
✔️ Solution
the main server will have the configuration database and the status
Probes will connect via Web Sockets / HTTP 2.0 to the server (Client to server)
Probe will pull the configuration assigned to him and provide consolidated status every X Seconds
The server can use Redis to hold the data to improve performance alongside the Database or as a replacement
❓ Alternatives
No response
📝 Additional Context
No response
@discostur commented on GitHub (Jun 2, 2023):
Would be really nice to see this feature! Having separate probes on different locations all over the world would be a real benefit!
@CommanderStorm commented on GitHub (Jun 2, 2023):
@elimelamed is this a duplicate of #84
If no, could you make the difference between this proposal and #84 more clear?
If yes, could you close this issue (duplicate issues are not benefitial for project health 😉)
@CommanderStorm commented on GitHub (Jun 2, 2023):
@discostur
Don't the current push-monitors solve this usecase already?
@pythonmandev commented on GitHub (Sep 1, 2023):
Can not find a HOWTO about push monitor :(
@CommanderStorm commented on GitHub (Sep 1, 2023):
@pythonmandev

What are you stuck on? (Where do we need to improve the UI-Helptexts?)