-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Main and Sub / Push monitor status to another uptime kuma instance #1503
Comments
So you have 2 instances. One of them is publicly accessible. The private one monitors some services and you want to send this data to the public one. Am I along the right lines here? |
Exactly. |
Is there any particular reason why not to make the internal server publicly accessible? It is possible to configure which monitors appear on the public status page and any that you don't want to make accessible are behind the login screen. It doesn't really make sense to me why you would have two separate instances like this. Perhaps I am missing something here. |
The main idea is that my smart home is nearly completely offline. So I don't want that a tool shows itself tonthe outside. If a public instance get the informations pushed, then i think it's more difficult to understand for an attacker where it comes from Yeah I'm a bit paranoid, but this scenario would also work for other networktypes i think ¯_(ツ)_/¯ |
In my very limited understanding of this topic i think it would be a good solution to create an notification service as counterpart to the push monitor. |
I see where your coming from with this but it does seem a bit niche. There could possibly be a use for pushing to different types of monitors in an effort to integrate with existing infrastructure but we already have the Prometheus metrics page for that. Perhaps it might be worth looking into site to site VPNs or SSH tunnelling. Of course, this is just my opinion and I would be interested in seeing what others think. |
Being able to have one public and several private would be amazing. |
Another good reason for this feature is the docker monitor. |
@DunklerPhoenix |
🏷️ Feature Request Type
New Monitor, Other
🔖 Feature description
Two instances of uptime kuma are running.
One on local network and the other on a server on the internet.
It would be great if the local uptime kuma instance can push the monitor status to the public instance.
✔️ Solution
This could be done in form of a special notification service I think.
❓ Alternatives
Or as a complete new system
📝 Additional Context
I don't want to publish an uptime kuma instance that has access to my smart home mqtt server (e.g.)
So it would be great if there is a Main and Sub system or a reporting system between multiple instances.
The text was updated successfully, but these errors were encountered: