Distributed Monitoring #2160

Closed
opened 2026-02-28 02:44:57 -05:00 by deekerman · 5 comments
Owner

Originally created by @elimelamed on GitHub (May 4, 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

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

Originally created by @elimelamed on GitHub (May 4, 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 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_
deekerman 2026-02-28 02:44:57 -05:00
Author
Owner

@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!

@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!
Author
Owner

@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): @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 😉)
Author
Owner

@CommanderStorm commented on GitHub (Jun 2, 2023):

@discostur

Having separate probes on different locations all over the world would be a real benefit!

Don't the current push-monitors solve this usecase already?

@CommanderStorm commented on GitHub (Jun 2, 2023): @discostur > Having separate probes on different locations all over the world would be a real benefit! Don't the current push-monitors solve this usecase already?
Author
Owner

@pythonmandev commented on GitHub (Sep 1, 2023):

Can not find a HOWTO about push monitor :(

@pythonmandev commented on GitHub (Sep 1, 2023): Can not find a HOWTO about push monitor :(
Author
Owner

@CommanderStorm commented on GitHub (Sep 1, 2023):

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

@CommanderStorm commented on GitHub (Sep 1, 2023): @pythonmandev What are you stuck on? (Where do we need to improve the UI-Helptexts?) ![image](https://github.com/louislam/uptime-kuma/assets/26258709/7f4e3f72-d272-4bc6-9e06-4390660bf18e)
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#2160
No description provided.