starred/uptime-kuma

Fork 0

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

[groups] Monitor critical flag to replace 'Partially Degraded Service' with 'Full Service Outage' #2248

New issue

Closed

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

deekerman commented

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

Owner

Originally created by @kub3let on GitHub (Jun 10, 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

The Status Page on top shows All Systems Operational or Partially Degraded Service but there is never really a Degraded Service or Full Service Outage message, since that requires all Monitors to be down ?

I have a bunch of Monitors and some like Router or Firewall can be interpreted as if they are down nothing works. There are still other Monitors like redundancy or offsite services that will always be up though.

I think it would be great if we had a Critical Service checkbox (or dropdown with levels?) on the Monitor.

✔️ Solution

Adding a checkbox Critical Service on Monitors.

If this is checked and the Monitor is on the Status Page with Status down the heading message changes to Full Service Outage with red error symbol.

Actual message e.g. Full Service Outage to be defined.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @kub3let on GitHub (Jun 10, 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 The Status Page on top shows `All Systems Operational` or `Partially Degraded Service` but there is never really a `Degraded Service` or `Full Service Outage` message, since that requires all Monitors to be down ? I have a bunch of Monitors and some like `Router` or `Firewall` can be interpreted as if they are down nothing works. There are still other Monitors like redundancy or offsite services that will always be up though. I think it would be great if we had a `Critical Service` checkbox (or dropdown with levels?) on the Monitor. ### ✔️ Solution Adding a checkbox `Critical Service` on Monitors. If this is checked and the Monitor is on the Status Page with Status `down` the heading message changes to `Full Service Outage` with red error symbol. Actual message e.g. `Full Service Outage` to be defined. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

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

closed this issue
added the
feature-request

question

A:monitor
labels

deekerman commented

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

Author

Owner

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

Related #2487 #2474

Imo #2693 blocks #1236 which blocks this change

@CommanderStorm commented on GitHub (Jun 10, 2023): Related #2487 #2474 Imo #2693 blocks #1236 which blocks this change

deekerman commented

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

Author

Owner

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

I would argue against adding such a checkbox (additional clutter), but rather change the message to Degraded Service if all monitors in a status page are down.
(this would also not be blocked by grouping)

@CommanderStorm commented on GitHub (Jun 10, 2023): I would argue against adding such a checkbox (additional clutter), but rather change the message to `Degraded Service` if all monitors in a status page are down. (this would also not be blocked by grouping)

deekerman commented

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

Author

Owner

@kub3let commented on GitHub (Jun 10, 2023):

Seems reasonable, I will wait for the pr's to be merged and then see if I can implement this feature.

@kub3let commented on GitHub (Jun 10, 2023): Seems reasonable, I will wait for the pr's to be merged and then see if I can implement this feature.

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Dec 1, 2023):

@kub3let
I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/1089
Oppinions?

@CommanderStorm commented on GitHub (Dec 1, 2023): @kub3let I think, we should track this issue in https://github.com/louislam/uptime-kuma/issues/1089 Oppinions?

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Jan 19, 2024):

Continuing to track this in https://github.com/louislam/uptime-kuma/issues/1089 and related issues tagged with [groups]

=> closing as a duplicate

@CommanderStorm commented on GitHub (Jan 19, 2024): Continuing to track this in https://github.com/louislam/uptime-kuma/issues/1089 and related issues tagged with `[groups]` => closing as a duplicate

deekerman referenced this issue

2026-02-28 02:54:43 -05:00

Docker container monitoring #2433