starred/uptime-kuma

Fork 0

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

Status pages don't notify of connectivity loss to the server #3177

New issue

Open

opened 2026-02-28 03:20:42 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 03:20:42 -05:00

Owner

Originally created by @maxzapp on GitHub (Mar 6, 2024).

The internetconnection between browser and uptime-server is not monitored. If the connection is broken all the monitors stay "green"

🏷️ Feature Request Type

New monitor

🔖 Feature description

The connection between browser and uptime-server must be monitored and in any loss of connection this must be visible reported to avoid monitoring of outdates statuses of other monitors.

✔️ Solution

Add own monitor or generic build in kind of heartbeat, watchdog.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @maxzapp on GitHub (Mar 6, 2024). ### 📑 I have found these related issues/pull requests The internetconnection between browser and uptime-server is not monitored. If the connection is broken all the monitors stay "green" ### 🏷️ Feature Request Type New monitor ### 🔖 Feature description The connection between browser and uptime-server must be monitored and in any loss of connection this must be visible reported to avoid monitoring of outdates statuses of other monitors. ### ✔️ Solution Add own monitor or generic build in kind of heartbeat, watchdog. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman added the

feature-request

question

A:status-page

labels

2026-02-28 03:20:42 -05:00

deekerman commented

2026-02-28 03:20:45 -05:00

Author

Owner

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

I think what you are requesting is this red bar which shows up a few seconds after we loose connnectivity:

I am going to close this issue as resolved.
If there is something I missed, we can reopen

@CommanderStorm commented on GitHub (Mar 6, 2024): I think what you are requesting is this red bar which shows up a few seconds after we loose connnectivity: ![image](https://github.com/louislam/uptime-kuma/assets/26258709/77a08e3a-15f9-406d-bc5d-c535615a207d) I am going to close this issue as resolved. If there is something I missed, we can reopen

deekerman commented

2026-02-28 03:20:45 -05:00

Author

Owner

@maxzapp commented on GitHub (Mar 6, 2024):

Hi, ok you right on the dashboard is a red line but on the status pages is nothing like this

@maxzapp commented on GitHub (Mar 6, 2024): Hi, ok you right on the dashboard is a red line but on the status pages is nothing like this

deekerman commented

2026-02-28 03:20:45 -05:00

Author

Owner

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

Could you edit your description and the issue title to be closer to the actual issue? ^^
(I think this could be a good first issue, but would need a better description to be tagged as such)

@CommanderStorm commented on GitHub (Mar 6, 2024): Could you edit your description and the issue title to be closer to the actual issue? ^^ (I think this could be a good first issue, but would need a better description to be tagged as such)

deekerman commented

2026-02-28 03:20:45 -05:00

Author

Owner

@chakflying commented on GitHub (Mar 6, 2024):

I don't see this as a "good first issue", since it's not entirely clear how to handle this and display appropriate information. Since we don't use a persistent connection for the status pages, we'll have to go off of some number of retries for the perodic data fetch? And would we still use a red banner, or somehow clear the invalid data from the frontend?

@chakflying commented on GitHub (Mar 6, 2024): I don't see this as a "good first issue", since it's not entirely clear how to handle this and display appropriate information. Since we don't use a persistent connection for the status pages, we'll have to go off of some number of retries for the perodic data fetch? And would we still use a red banner, or somehow clear the invalid data from the frontend?

deekerman commented

2026-02-28 03:20:45 -05:00

Author

Owner

@maxzapp commented on GitHub (Mar 7, 2024):

Hi, mayby my description was not perfect, but it seems the connection is "monitored" somewhow and failure is shown on dashboard, all i think what is needed is just to show the same red line on status pages as on dashboard. So it is more of a bug right now in my eyes. But i think a simple red titlebar is not "good" enough because if the browser is configured in full view i am not shure if it is shown then. So this "event" must be more "in your face" stile

@maxzapp commented on GitHub (Mar 7, 2024): Hi, mayby my description was not perfect, but it seems the connection is "monitored" somewhow and failure is shown on dashboard, all i think what is needed is just to show the same red line on status pages as on dashboard. So it is more of a bug right now in my eyes. But i think a simple red titlebar is not "good" enough because if the browser is configured in full view i am not shure if it is shown then. So this "event" must be more "in your face" stile