starred/uptime-kuma

Fork 0

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

Heartbeat Monitor Animation for Status Page #432

New issue

Closed

opened 2026-02-28 01:46:23 -05:00 by deekerman · 5 comments

deekerman commented

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

Owner

Originally created by @avancebt on GitHub (Oct 18, 2021).

I noticed a potential problem with the status page that showed up for me when the uptime-kuma docker service stopped working.
The status page remained responsive, and showed everything as okay and green - but it was not actually checking.
Once all the hearbeat pills have been filled, there is no visual way of determining that the status monitor is actually doing anything, you just see every pill filled in as green.
If there was an animation for each heartbeat pill as it was been checked (maybe it spins) - and some way of showing the results 'shfting' to the the left (maybe a time period on the X axis or something) then I would have more confidence that uptime-kuma is working and hasn't frozen up.

Originally created by @avancebt on GitHub (Oct 18, 2021). I noticed a potential problem with the status page that showed up for me when the uptime-kuma docker service stopped working. The status page remained responsive, and showed everything as okay and green - but it was not actually checking. Once all the hearbeat pills have been filled, there is no visual way of determining that the status monitor is actually doing anything, you just see every pill filled in as green. If there was an animation for each heartbeat pill as it was been checked (maybe it spins) - and some way of showing the results 'shfting' to the the left (maybe a time period on the X axis or something) then I would have more confidence that uptime-kuma is working and hasn't frozen up.

deekerman

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

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 01:46:28 -05:00

Author

Owner

@markdesilva commented on GitHub (Oct 18, 2021):

How does the UK docker stop working but you can still view the status page?

@markdesilva commented on GitHub (Oct 18, 2021): How does the UK docker stop working but you can still view the status page?

deekerman commented

2026-02-28 01:46:28 -05:00

Author

Owner

@avancebt commented on GitHub (Oct 18, 2021):

How does the UK docker stop working but you can still view the status page?

Hi,
I guess the whole docker didn't stop working - probably just a sub module/service, but I had to stop and restart the docker instance for the heartbeat monitor to begin moving again (I could still interact just fine with the dashboard as well before restarting docker etc)
I knew it had failed, because I got an alert for a monitored website being down, except it was perfectly fine, and after that moment, the heartbeat pills didn't move across to the left (the amber and red warning pills stayed in the same posiiton).
Now I could tell in this instance, but if the hearbeat service/status page were showing all 100% up and it stopped updating, then it would be very difficult to tell.

@avancebt commented on GitHub (Oct 18, 2021): > How does the UK docker stop working but you can still view the status page? Hi, I guess the whole docker didn't stop working - probably just a sub module/service, but I had to stop and restart the docker instance for the heartbeat monitor to begin moving again (I could still interact just fine with the dashboard as well before restarting docker etc) I knew it had failed, because I got an alert for a monitored website being down, except it was perfectly fine, and after that moment, the heartbeat pills didn't move across to the left (the amber and red warning pills stayed in the same posiiton). Now I could tell in this instance, but if the hearbeat service/status page were showing all 100% up and it stopped updating, then it would be very difficult to tell.

deekerman commented

2026-02-28 01:46:28 -05:00

Author

Owner

@gaby commented on GitHub (Oct 18, 2021):

Duplicate from #546 Please use the bug template when reporting issues.

@gaby commented on GitHub (Oct 18, 2021): Duplicate from #546 Please use the bug template when reporting issues.

deekerman commented

2026-02-28 01:46:28 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jul 26, 2023):

@avancebt

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/546 which was resolved in 1.9.1. => I think this is also resolved.
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?) ^^

@CommanderStorm commented on GitHub (Jul 26, 2023): @avancebt I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/546 which [was resolved in `1.9.1`](https://github.com/louislam/uptime-kuma/issues/546#issuecomment-947285722). => I think this is also resolved. 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?) ^^

deekerman commented

2026-02-28 01:46:28 -05:00

Author

Owner

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

Closing as resolved in 1.9.1

@CommanderStorm commented on GitHub (Dec 3, 2023): Closing as resolved in `1.9.1`

deekerman referenced this issue

2026-02-28 01:54:26 -05:00

Make the DNS check also validate a specific record value #677

deekerman referenced this issue

2026-02-28 01:54:26 -05:00