Monitoring Agent for multi location status #2023

New issue

Closed

opened 2026-02-28 02:40:33 -05:00 by deekerman · 4 comments

deekerman commented

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

Owner

Originally created by @wzrdtales on GitHub (Mar 21, 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

Sometimes outages are only partial across the internet, to notice that it is useful to set up multiple agents at different locations, each independently executing the same monitoring actions.

✔️ Solution

An agent that executes only actual actions and communicates them back to the master.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @wzrdtales on GitHub (Mar 21, 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 Sometimes outages are only partial across the internet, to notice that it is useful to set up multiple agents at different locations, each independently executing the same monitoring actions. ### ✔️ Solution An agent that executes only actual actions and communicates them back to the master. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

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

closed this issue
added the
feature-request

A:monitor
labels

deekerman commented

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

Author

Owner

@wzrdtales commented on GitHub (Mar 21, 2023):

Right now you could only abuse the proxy function for this, but it would require multiple monitors for the same service and is limited to HTTP only.

@wzrdtales commented on GitHub (Mar 21, 2023): Right now you could only abuse the proxy function for this, but it would require multiple monitors for the same service and is limited to HTTP only.

deekerman commented

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

Author

Owner

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

Duplicate of #84

@CommanderStorm commented on GitHub (Dec 6, 2023): Duplicate of #84

deekerman commented

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

Author

Owner

@robcarvaj commented on GitHub (Mar 21, 2024):

@wzrdtales Hi, I was wondering if you have any guidance on how to do this? "Right now you could only abuse the proxy function for this, but it would require multiple monitors for the same service and is limited to HTTP only." I'm not familiar on how that setup would look like. For now, that would be sufficient enough for my environment until https://github.com/louislam/uptime-kuma/issues/84 gets implemented.

@robcarvaj commented on GitHub (Mar 21, 2024): @wzrdtales Hi, I was wondering if you have any guidance on how to do this? "Right now you could only abuse the proxy function for this, but it would require multiple monitors for the same service and is limited to HTTP only." I'm not familiar on how that setup would look like. For now, that would be sufficient enough for my environment until https://github.com/louislam/uptime-kuma/issues/84 gets implemented.

deekerman commented

2026-02-28 02:40:39 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Mar 21, 2024):

@robcarvaj
Have you looked at the push-monitor?
Said monitor should be enough to implement the functionality you are looking for (though not as "simple"/convenient as #84)

For code samples on how to achieve this, please look at https://github.com/louislam/uptime-kuma/tree/master/extra/push-examples

@CommanderStorm commented on GitHub (Mar 21, 2024): @robcarvaj Have you looked at the `push`-monitor? Said monitor should be enough to implement the functionality you are looking for (though not as "simple"/convenient as #84) For code samples on how to achieve this, please look at https://github.com/louislam/uptime-kuma/tree/master/extra/push-examples