Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remote monitors #3845

Closed
1 task done
koehn opened this issue Oct 4, 2023 · 1 comment
Closed
1 task done

Remote monitors #3845

koehn opened this issue Oct 4, 2023 · 1 comment
Labels
feature-request Request for new features to be added

Comments

@koehn
Copy link

koehn commented Oct 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

What I’m interested in is a monitor that runs from a remote location (in addition to where uptime-kuma is running). My challenge is I get a lot of false positives running uptime-kuma in my house monitoring my remote servers. I’d like to have monitors running remotely and only raise an alert if two or more monitors report a connectivity problem.

✔️ Solution

  1. Separate the monitoring app from the notification/UI app.
  2. Allow the monitoring app to be installed, and have it poll an API on the main instance of the app to get the list of services to monitor. When a service fails, call another API to report the failure.
  3. Have the backend confirm that n monitors (configurable) must report the service as down before sending a notification.

❓ Alternatives

Just installing it remotely and sending notifications from two spots, but that’s kind of nasty.

I could also solve my problem by disabling notifications if the main app cannot ping a known available host (e.g. Google), as that would indicate my ISP was down, not my services.

Still, multiple locations would be better.

📝 Additional Context

This also helps prevent spurious errors I get when I lose internet connectivity at home where my monitor runs.

@koehn koehn added the feature-request Request for new features to be added label Oct 4, 2023
@CommanderStorm
Copy link
Collaborator

CommanderStorm commented Oct 4, 2023

I think this is a duplicate of #84 (and its related duplicate)
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

Pkease also note that this can be solved by using push monitors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features to be added
Projects
None yet
Development

No branches or pull requests

2 participants