Customizable Heartbeat trail intervals on Status Page #4519

New issue

Closed

opened 2026-02-28 04:05:52 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 04:05:52 -05:00

Owner

Originally created by @fsedarkalex on GitHub (Dec 9, 2025).

I found a few requests relating tot he percentage but not to the heartbeat trail

🏷️ Feature Request Type

Status-page

🔖 Feature description

Currently there is a fixed amount of heartbeas visibel on the SP. So visible range = 60*monitor interval.

My sugestion it to add a few options.

✔️ Solution

What I would find very handy is multiple options:

Last 60 (as it is currently)
Last [N] (settable timerange) evenly spread (shows the next nearest heartbeat available every [N]/60)
Variable intervals, configurable (like show latest 5, next x every y'th heartbeat and so on)

Maybe we should not use the individual heartbeat but the worst in the specific timerange?

❓ Alternatives

For Variable intervals, as the proposed soution is likely hard to implement, it could probably also be an option to use a fixed model like

last 10 heartbeats, then
next 10 every 2nd heartbeat
next 10 every 5th heartbeat
next 10 every 10th heartbeat
next 10 every 25th heartbeat
next 10 every 50th heartbeat

at a usual interval of 120sec this makes a total overview over last ~30h

📝 Additional Context

Regarding the option 2, think of a sensor checking every 60 seconds and the range set to 3h. The interface would then show the marked heartbeats

... 1:00 1:01 1:02 1:03 1:04 1:05 1:06 1:07 1:08 1:09 1:10 1:11 1:12 1:13 1:14 1:15

Originally created by @fsedarkalex on GitHub (Dec 9, 2025). ### 📑 I have found these related issues/pull requests I found a few requests relating tot he percentage but not to the heartbeat trail ### 🏷️ Feature Request Type Status-page ### 🔖 Feature description Currently there is a fixed amount of heartbeas visibel on the SP. So visible range = 60*monitor interval. My sugestion it to add a few options. ### ✔️ Solution What I would find very handy is multiple options: - Last 60 (as it is currently) - Last [N] (settable timerange) evenly spread (shows the next nearest heartbeat available every [N]/60) - Variable intervals, configurable (like show latest 5, next x every y'th heartbeat and so on) Maybe we should not use the individual heartbeat but the worst in the specific timerange? ### ❓ Alternatives For Variable intervals, as the proposed soution is likely hard to implement, it could probably also be an option to use a fixed model like - last 10 heartbeats, then - next 10 every 2nd heartbeat - next 10 every 5th heartbeat - next 10 every 10th heartbeat - next 10 every 25th heartbeat - next 10 every 50th heartbeat at a usual interval of 120sec this makes a total overview over last ~30h ### 📝 Additional Context Regarding the option 2, think of a sensor checking every 60 seconds and the range set to 3h. The interface would then show the marked heartbeats ... **1:00** 1:01 1:02 **1:03** 1:04 1:05 **1:06** 1:07 1:08 **1:09** 1:10 1:11 **1:12** 1:13 1:14 **1:15**

deekerman

2026-02-28 04:05:52 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 04:05:57 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 9, 2025):

Closing as a duplicate of #1888
If you have content advise, please raise that there.

If you have engineeing time to invest into getting https://github.com/louislam/uptime-kuma/pull/5916 into a mergable state..

@CommanderStorm commented on GitHub (Dec 9, 2025): Closing as a duplicate of #1888 If you have content advise, please raise that there. If you have engineeing time to invest into getting https://github.com/louislam/uptime-kuma/pull/5916 into a mergable state..