Configurable Range heartbeat bar (`7`/`30`/`60`/`90`/`180`/`365` days)

[Vecsy]

⚠️ 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

Please add the ability to set the length of days for the heartbeat bar on the status page.

✔️ Solution

In Uptime-Robot, the heartbeat bar indicator shows a red bar on the day an event was logged. It'd be very useful to set the length/amount of days for the heartbeat bar to show 30, 60 or 90 days.

❓ Alternatives

No response

📝 Additional Context

No response

[zigazajc007]

There are multiple ways to implement this.

Should the owner of the status panel decide for how many days stats would be shown or each visitor would have the option to change this?

This is how I would want it:

Lets say that the owner choose to show data for a month. So each line would present 1 day. And if in the first day uptime has been 100% then this line should be colored green. Now lets imagine that next day uptime has been 98%, so second line should be colored yellow/orange and when you hover over the line it will say date and uptime in %. But then if you click on this line it will show 24 lines (Each line corresponding to the hour in this day), so user can see that all lines are green except 5th line is orange, that would mean downtime has happened at 5am. And if you click on it, then it can also show 60 lines (Each line corresponding to the minute), but if you set hearthbeat to 5 minutes then it can show only 12 lines and each line represending 5 minutes. So you can then see when the downtime happened.

1. Date + Uptime in %

2. Hour + Uptime in %

3. Hour + Minute

Note that in this examples I didn't changed the number of lines. But I hope I have explained it good enough.

[wiwi-websolutions]

+1

[AyupMike]

This would be so useful for us - 30 or even 60/90 day history.

[Peter1994]

+1

[wesco73]

+1

[bastoune]

+1

[Vecsy]

@louislam - you reckon we’ll get this added soon?On 21 Sep 2022, at 12:19, bastoune @.***> wrote: +1

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[jhambach]

Having history is a great way to display previous uptime. Right now there's only a short period of history you can view.

Edit: User was likely seraching for this issue instead:

• https://github.com/louislam/uptime-kuma/issues/1984

[feriahmad]

+1

[dib0]

+1 This would really help me and make a really good application even better!

[hsankala]

+1

[ouquoi]

For sure this use case will put uptime kuma to the next level ! +1

[CommanderStorm]

@ouquoi @hsankala @dib0 @feriahmad @Vecsy @bastoune @wesco73 @Peter1994 @wiwi-websolutions

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.

[Boyan-LF]

For company for which I work, this is the most important issue to be resolved, so we wouldn't choose BetterStack status pages instead of Uptime Kuma which we initially like..

So is there a particular donation amount which would be a motivator for you to expedite solution for Uptime Kuma status page bars to have 7/30/60/90/180/365 days options for length of heartbeat bars..?

[samumatic]

Isn't this the same issue as #3264 ? It could be merged.

[casudo]

+1

[CommanderStorm]

@casudo

Please see above:

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, as always: Pull Requests welcome.

[plgonzalezrx8]

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.

[CommanderStorm]

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.