Yearly uptime

[lino-silva]

Is it a duplicate question?
Not that I could find.

Is your feature request related to a problem? Please describe.
I'd love to be able to set yearly SLAs for my services, but uptime percentage is being described in a 24-hour or a 30-day timeframe - just like uptime robot. I checked in the source code you've hardcoded those in the UI (didn't check the backend code but assumed it's the same).

Describe the solution you'd like
Ideally I'd like to define with environment variables or something like that which intervals I'd like to see for each service - I know different people have different needs, so in no way I'm trying to substitute the timeframes you've already got in place.

Describe alternatives you've considered
I tried using Prometheus/Grafana, but Uptime Kuma is sooooooooooooooo much better and well suited to my use case.

Additional context
N/A

[luisxiaomai]

Yearly uptime +1。
By the way, @lino-silva can you share how you did for service uptime monitoring by Prometheus/Grafana?

[lino-silva]

I didn't! That's the thing hahah.

[jtagcat]

Also, the uptime percentage should be more accurate than 4 decimals (99,99).

[FlorianMifsud]

Why not be able to choose 1Day/1Week/1(6)Month/1Year ?

[hanselsen]

This would be a great feature!

[jtagcat]

GitHub Etiquette

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

[BBaoVanC]

This might be related to #986 (and is a couple months older than #986)

[hanselsen]

@louislam how can we get this feature to be implemented in the next milestone?

[jarhainx]

This is the only feature I'm missing!
@louislam Would it be possible to add it?
Thank!

[CommanderStorm]

@jarhainx @hanselsen

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.

Note that there is #2750 which discusses a few approaches.
Said PR is on the Roadmap for the v2.0 release.

[CommanderStorm]

#2750 was merged and will be available in the v2.0-release
=> I am going to close this as resolved

[mnmami]

@CommanderStorm thanks for merging. The release has no due date, any speculation when v 2.0 will be released?

[CommanderStorm]

When it's done and all bugs are addressed.
See #4171