starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Sending "I'm alive message" - get health status from other uptime-kuma instances #1485

New issue

Closed

opened 2026-02-28 02:22:54 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 02:22:54 -05:00

Owner

Originally created by @MajorTomDE on GitHub (Oct 16, 2022).

⚠️ 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

I'm running two linux servers: One within my private LAN and one "public" one the internet.

My challenge is to know the health of my LAN uptime-kuma without VPN Connection.
Public uptime kuma has no access to LAN uptime kuma.

✔️ Solution

How about to implement a "I'm alive" function?

uptime-kuma is calling a URL (e.g. the uptime-kuma push url) all x seconds and reports his alive status.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @MajorTomDE on GitHub (Oct 16, 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 Other ### 🔖 Feature description I'm running two linux servers: One within my private LAN and one "public" one the internet. My challenge is to know the health of my LAN uptime-kuma without VPN Connection. Public uptime kuma has no access to LAN uptime kuma. ### ✔️ Solution How about to implement a "I'm alive" function? uptime-kuma is calling a URL (e.g. the uptime-kuma push url) all x seconds and reports his alive status. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:22:54 -05:00

closed this issue
added the
feature-request

A:monitor
labels

deekerman commented

2026-02-28 02:23:02 -05:00

Author

Owner

@rezzorix commented on GitHub (Oct 16, 2022):

Have you considered something like this:
https://github.com/louislam/uptime-kuma/wiki/Prometheus-Integration ?

@rezzorix commented on GitHub (Oct 16, 2022): Have you considered something like this: https://github.com/louislam/uptime-kuma/wiki/Prometheus-Integration ?

deekerman commented

2026-02-28 02:23:02 -05:00

Author

Owner

@MajorTomDE commented on GitHub (Oct 25, 2022):

I played with Prometheus over the weekend and it is too "big" for my purposes.

The easiest way for my scenario would be an option in uptime kuma to send a "I'm alive message" ... Also to run a URL

@MajorTomDE commented on GitHub (Oct 25, 2022): I played with Prometheus over the weekend and it is too "big" for my purposes. The easiest way for my scenario would be an option in uptime kuma to send a "I'm alive message" ... Also to run a URL

deekerman commented

2026-02-28 02:23:02 -05:00

Author

Owner

@kevingruesser commented on GitHub (Oct 27, 2022):

That's exactly what I need too.

A reversed push monitoring runs on the public server and a push alarm is sent on the private server if a service cannot be reached.

@kevingruesser commented on GitHub (Oct 27, 2022): That's exactly what I need too. A reversed push monitoring runs on the public server and a push alarm is sent on the private server if a service cannot be reached.

deekerman commented

2026-02-28 02:23:02 -05:00

Author

Owner

@whgDosumi commented on GitHub (Jan 30, 2023):

Just chiming in and saying I'd like this feature. I use a cloud hosted uptime kuma but some of the services I'd like to monitor are private, and I'd rather not give the remote server access to the internal network.

To work around this, I just set up a "push" monitor in uptime kuma, and set up a cron job internally to monitor the services and call the monitor url if successful. Using Uptime Kuma to set up the monitors would be easier than this, but it gets the job done for me.

@whgDosumi commented on GitHub (Jan 30, 2023): Just chiming in and saying I'd like this feature. I use a cloud hosted uptime kuma but some of the services I'd like to monitor are private, and I'd rather not give the remote server access to the internal network. To work around this, I just set up a "push" monitor in uptime kuma, and set up a cron job internally to monitor the services and call the monitor url if successful. Using Uptime Kuma to set up the monitors would be easier than this, but it gets the job done for me.

deekerman commented

2026-02-28 02:23:02 -05:00

Author

Owner

@MajorTomDE commented on GitHub (Feb 3, 2023):

@kevingruesser @whgDosumi
Thanks for your answers. I tried the last months a few "workarounds", e.g. with cronjobs.
But this is not really comfortable.
Unfortunately I am not a developer, otherwise I would create a pull request myself.

For me the easiest solution would be a new function in the settings:
"Call" I'm Alive URL:

Active Yes/No
URL
Seconds

Function: When active, Uptime Kuma "calls" all x seconds the URL. Thats it ;-)

@MajorTomDE commented on GitHub (Feb 3, 2023): @kevingruesser @whgDosumi Thanks for your answers. I tried the last months a few "workarounds", e.g. with cronjobs. But this is not really comfortable. Unfortunately I am not a developer, otherwise I would create a pull request myself. For me the easiest solution would be a new function in the settings: "Call" I'm Alive URL: 1. Active Yes/No 2. URL 3. Seconds Function: When active, Uptime Kuma "calls" all x seconds the URL. Thats it ;-)

deekerman commented

2026-02-28 02:23:02 -05:00

Author

Owner

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

@MajorTomDE
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): @MajorTomDE 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.