multiple node/server checker #1421

New issue

Closed

opened 2026-02-28 02:20:39 -05:00 by deekerman · 1 comment

deekerman commented

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

Owner

Originally created by @FosterG4 on GitHub (Sep 22, 2022).

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

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Notification, New Monitor, UI Feature, Other

🔖 Feature description

multiple node/server checker,

add multiple proxy or can add node cheker to master cheker

sample : check ping from different location us,uk,singapore

web ui dashboard :
ping from us : 56ms
ping from uk : 70ms
ping from singapore : 100ms

✔️ Solution

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @FosterG4 on GitHub (Sep 22, 2022). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Notification, New Monitor, UI Feature, Other ### 🔖 Feature description multiple node/server checker, add multiple proxy or can add node cheker to master cheker sample : check ping from different location us,uk,singapore web ui dashboard : ping from us : 56ms ping from uk : 70ms ping from singapore : 100ms ### ✔️ Solution no ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

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

closed this issue
added the
feature-request

A:monitor
labels

deekerman commented

2026-02-28 02:20:47 -05:00

Author

Owner

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

@FosterG4
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in #84 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.

@CommanderStorm commented on GitHub (Dec 7, 2023): @FosterG4 We are consolidating duplicate issues a bit to make issue management easier. I think, we should track this issue in #84 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo) ⇒ I am going to close this as a duplicate.