starred/uptime-kuma

Fork 0

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

[Feature]: Change status #493

New issue

Closed

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

deekerman commented

2026-02-28 01:48:19 -05:00

Owner

Originally created by @petercipriano-wtv on GitHub (Oct 29, 2021).

📝 Describe your problem

Is there a way to have an option like Operational instead of the bar in the status page?

🐻 Uptime-Kuma version

1.9.1

💻 Operating System

Ubuntu

🌐 Browser

Chrome

🐋 Docker

20.10.9

🏷️ Docker Image Tag

1.91

🟩 NodeJS Version

No response

👀 Have you spent some time to check if this question has been raised before?

I checked and didn't find similar question

🛡️ Security Policy

I agree to have read this project Security Policy

Originally created by @petercipriano-wtv on GitHub (Oct 29, 2021). ### 📝 Describe your problem Is there a way to have an option like Operational instead of the bar in the status page? ### 🐻 Uptime-Kuma version 1.9.1 ### 💻 Operating System Ubuntu ### 🌐 Browser Chrome ### 🐋 Docker 20.10.9 ### 🏷️ Docker Image Tag 1.91 ### 🟩 NodeJS Version _No response_ ### 👀 Have you spent some time to check if this question has been raised before? - [X] I checked and didn't find similar question ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy)

deekerman

2026-02-28 01:48:19 -05:00

closed this issue
added the
Stale

help
labels

deekerman commented

2026-02-28 01:48:27 -05:00

Author

Owner

@deefdragon commented on GitHub (Oct 29, 2021):

To confirm, you are referring to how Cloudflare status for example has "Operational" vs "Re-Routed" etc. whereas UK only has the heartbeat bars?

Assuming the answer is yes, I think it wouldn't be too hard to use most recent ping to set a status.

Some brainstorming

I'm thinking that it would be best if this and the bar were separately toggled as to if they show up. That way you could have none, either, or both showing.

I'm thinking Operational, Degraded, Down, and Recovering as some potential starting terms, but what each of them means is potentially up for debate.

Down: The service has not responded to a ping for N pings. (Uses the retry number in the monitor to define down?)
Degraded: At least one ping has been missed continuously in the last N. (or, optionally, the ping time is above a specific threshold)
Recovering: Reached the state of down, but is now responding to pings again. (Or, reached a state of down/degraded, but has been green for the most recent half of pings)
Operational: all good in last N pings

Some far future considerations:

Would it be possible to set rules as to when the different terms are used? Then other statuses could be defined by the user instead of hard coded.
Would it be possible to use these states to trigger notifications?
Then a notification could go out if the monitor has become degraded instead of just down. It Would depend on custom rules again, and would likely require notification configuration options (#233) too.

@deefdragon commented on GitHub (Oct 29, 2021): To confirm, you are referring to how [Cloudflare status for example](https://www.cloudflarestatus.com/) has "Operational" vs "Re-Routed" etc. whereas UK only has the heartbeat bars? Assuming the answer is yes, I think it wouldn't be too hard to use most recent ping to set a status. ![cloudflare](https://user-images.githubusercontent.com/3053654/139487471-b3fa17d7-c9d4-4508-bcf8-98443b7dc204.png) ----- ### Some brainstorming I'm thinking that it would be best if this and the bar were separately toggled as to if they show up. That way you could have none, either, or both showing. I'm thinking `Operational`, `Degraded`, `Down`, and `Recovering` as some potential starting terms, but what each of them means is potentially up for debate. Down: The service has not responded to a ping for N pings. (Uses the retry number in the monitor to define down?) Degraded: At least one ping has been missed continuously in the last N. (or, optionally, the ping time is above a specific threshold) Recovering: Reached the state of down, but is now responding to pings again. (Or, reached a state of down/degraded, but has been green for the most recent half of pings) Operational: all good in last N pings ------ ### Some far future considerations: Would it be possible to set rules as to when the different terms are used? Then other statuses could be defined by the user instead of hard coded. Would it be possible to use these states to trigger notifications? Then a notification could go out if the monitor has become degraded instead of just down. It Would depend on custom rules again, and would likely require notification configuration options (#233) too.

deekerman commented

2026-02-28 01:48:27 -05:00

Author

Owner

@petercipriano-wtv commented on GitHub (Oct 29, 2021):

@deefdragon exactly this is the one I'm talking about. I hope we can get this feature too :)

@petercipriano-wtv commented on GitHub (Oct 29, 2021): @deefdragon exactly this is the one I'm talking about. I hope we can get this feature too :)

deekerman commented

2026-02-28 01:48:27 -05:00

Author

Owner

@Kriiiiiiiz commented on GitHub (Nov 2, 2021):

Would be great to have it at UK

@Kriiiiiiiz commented on GitHub (Nov 2, 2021): Would be great to have it at UK

deekerman commented

2026-02-28 01:48:27 -05:00

Author

Owner

@deefdragon commented on GitHub (Nov 3, 2021):

Thinking about this some more, if we are messing around with what is displayed on the status pages, and configuring what gets displayed, we should probably be working on #818 at the same time as this. I think the files touched would be almost the same, so its worth considering at least.

This may be doable as part of #863, but I think its more likely to be done after.

@deefdragon commented on GitHub (Nov 3, 2021): Thinking about this some more, if we are messing around with what is displayed on the status pages, and configuring what gets displayed, we should probably be working on #818 at the same time as this. I think the files touched would be almost the same, so its worth considering at least. This may be doable as part of #863, but I think its more likely to be done after.

deekerman commented

2026-02-28 01:48:27 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 23, 2022):

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

@github-actions[bot] commented on GitHub (Sep 23, 2022): We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

deekerman commented

2026-02-28 01:48:27 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 26, 2022):

This issue was closed because it has been stalled for 2 days with no activity.

@github-actions[bot] commented on GitHub (Sep 26, 2022): This issue was closed because it has been stalled for 2 days with no activity.