Extend reporting duration separate from refresh frequency #3624

New issue

Closed

opened 2026-02-28 03:35:47 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 03:35:47 -05:00

Owner

Originally created by @mikeckennedy on GitHub (Sep 24, 2024).

None that I could find.

🏷️ Feature Request Type

Status-page

🔖 Feature description

When looking at the status pages, both the bars and more importantly the % uptime is based solely on the refresh frequency. This means you only see 30m - 2h of uptime status on the status page.

Can we please get a parameter to extend this? I'd love to have my refresh rate at 30s-60s, but my status page report the uptime for the last 30 days.

✔️ Solution

Add a setting to specify how large the time windows for the status pages are.

❓ Alternatives

Slow the refresh rate WAY down to a non-useful level. For example, I could set the refresh rate to ping the site every 11,160 sec, to get one month on the status page, but how representative of uptime will that be? Not very.

📝 Additional Context

Here is an example page:

https://uptimekuma.talkpython.fm/status/talk-python

See that it only shows between 30m-2h of uptime.

Originally created by @mikeckennedy on GitHub (Sep 24, 2024). ### 📑 I have found these related issues/pull requests None that I could find. ### 🏷️ Feature Request Type Status-page ### 🔖 Feature description When looking at the status pages, both the bars and more importantly the % uptime is based solely on the refresh frequency. This means you only see 30m - 2h of uptime status on the status page. Can we please get a parameter to extend this? I'd love to have my refresh rate at 30s-60s, but my status page report the uptime for the last 30 days. ### ✔️ Solution Add a setting to specify how large the time windows for the status pages are. ### ❓ Alternatives Slow the refresh rate WAY down to a non-useful level. For example, I could set the refresh rate to ping the site every 11,160 sec, to get one month on the status page, but how representative of uptime will that be? Not very. ### 📝 Additional Context Here is an example page: https://uptimekuma.talkpython.fm/status/talk-python See that it only shows between 30m-2h of uptime.

deekerman

2026-02-28 03:35:47 -05:00

closed this issue
added the
feature-request

A:status-page
labels

deekerman commented

2026-02-28 03:35:53 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Sep 25, 2024):

Duplicate of #1888.
Please see https://github.com/louislam/uptime-kuma/issues/1888#issuecomment-2068191172 for further context what is needed to activate this feature in v2.
Closing as a duplicate

@CommanderStorm commented on GitHub (Sep 25, 2024): Duplicate of #1888. Please see https://github.com/louislam/uptime-kuma/issues/1888#issuecomment-2068191172 for further context what is needed to activate this feature in v2. Closing as a duplicate

deekerman commented

2026-02-28 03:35:53 -05:00

Author

Owner

@mikeckennedy commented on GitHub (Sep 25, 2024):

Thanks @CommanderStorm I'm looking forward to v2 coming out.

@mikeckennedy commented on GitHub (Sep 25, 2024): Thanks @CommanderStorm I'm looking forward to v2 coming out.