starred/uptime-kuma

Fork 0

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

[Request] Status page: Customize the time period for the status ticks #2263

New issue

Closed

opened 2026-02-28 02:48:34 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-28 02:48:34 -05:00

Owner

Originally created by @JamesMenetrey on GitHub (Jun 13, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

Currently, status pages display ticks representing an interval of one minute. Consequently, users of status pages cannot see more than a period of time going above one hour.

This is quite limited when hosting services where we would like to build trust with our users and have a more holistic view of the uptime of our services.

✔️ Solution

Introduce a setting on the status page that would allow you to specify a time period covered by the ticks.

❓ Alternatives

An alternative setting would be to specify the duration of a tick (1 minute, 1 hour, 4 hour, 1 day, etc.).

📝 Additional Context

No response

Originally created by @JamesMenetrey on GitHub (Jun 13, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type UI Feature ### 🔖 Feature description Currently, status pages display ticks representing an interval of one minute. Consequently, users of status pages cannot see more than a period of time going above one hour. This is quite limited when hosting services where we would like to build trust with our users and have a more holistic view of the uptime of our services. ### ✔️ Solution Introduce a setting on the status page that would allow you to specify a time period covered by the ticks. ### ❓ Alternatives An alternative setting would be to specify the duration of a tick (1 minute, 1 hour, 4 hour, 1 day, etc.). ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:48:34 -05:00

closed this issue
added the
feature-request

A:status-page
labels

deekerman commented

2026-02-28 02:48:38 -05:00

Author

Owner

@ra-coder commented on GitHub (Jun 20, 2023):

Also would like to have this feature

@ra-coder commented on GitHub (Jun 20, 2023): Also would like to have this feature

deekerman commented

2026-02-28 02:48:40 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jun 20, 2023):

@ra-coder

Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder.
Issues are for discussing what needs to be done how by whom.
We use 👍🏻 on issues to prioritise work.

@CommanderStorm commented on GitHub (Jun 20, 2023): @ra-coder Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done how by whom. [We use 👍🏻 on issues to prioritise work](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc).

deekerman commented

2026-02-28 02:48:40 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Sep 27, 2023):

@JamesMenetrey
I think this is a duplicate of #1888
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 (Sep 27, 2023): @JamesMenetrey I think this is a duplicate of #1888 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 02:48:40 -05:00

Author

Owner

@JamesMenetrey commented on GitHub (Sep 28, 2023):

After reviewing #1888, this issue would satisfy this one if implemented. I cross my fingers it gets worked on soon! :)

@JamesMenetrey commented on GitHub (Sep 28, 2023): After reviewing #1888, this issue would satisfy this one if implemented. I cross my fingers it gets worked on soon! :)

deekerman commented

2026-02-28 02:48:40 -05:00

Author

Owner

@plgonzalezrx8 commented on GitHub (Apr 21, 2024):

Was this ever implemented? I cannot find this feature and want to create an issue but found this one, so I was wondering if there's a solution to this.

@plgonzalezrx8 commented on GitHub (Apr 21, 2024): Was this ever implemented? I cannot find this feature and want to create an issue but found this one, so I was wondering if there's a solution to this.

deekerman commented

2026-02-28 02:48:40 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Apr 21, 2024):

@plgonzalezrx8

From https://github.com/louislam/uptime-kuma/issues/1888#issuecomment-2068191172:

No it has not. In v1 the performance simply was not good enough to support this.

In v2, this should be possible.
See https://github.com/louislam/uptime-kuma/pull/4264 for further context on the PR that would enable configuring such a feature on the dashboard.
The status page does not have such a dependency, but needs somebody to implement it.
Our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

A synthetic benchmark which spawns some monitors and looks how the server handles it would likely be needed. See https://github.com/louislam/uptime-kuma/issues/4500 for how to get involved.

@CommanderStorm commented on GitHub (Apr 21, 2024): @plgonzalezrx8 From https://github.com/louislam/uptime-kuma/issues/1888#issuecomment-2068191172: > No it has not. In v1 the performance simply was not good enough to support this. > > In v2, this should be possible. See https://github.com/louislam/uptime-kuma/pull/4264 for further context on the PR that would enable configuring such a feature on the dashboard. The status page does not have such a dependency, but needs somebody to implement it. Our contribution guide is here: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md > > A synthetic benchmark which spawns some monitors and looks how the server handles it would likely be needed. See https://github.com/louislam/uptime-kuma/issues/4500 for how to get involved.