starred/uptime-kuma

Fork 0

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

[status page] Option to display only monitors that are down #2044

New issue

Closed

opened 2026-02-28 02:41:10 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-28 02:41:10 -05:00

Owner

Originally created by @Piste on GitHub (Mar 27, 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

I have more than 20 monitors, I'd like to see only those that are down on the dashboard view by selecting the appropriate filter.

✔️ Solution

Offer a filter or a checkbox, maybe in the left panel, that makes it possible to filter out monitors that are up.

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @Piste on GitHub (Mar 27, 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 I have more than 20 monitors, I'd like to see only those that are down on the dashboard view by selecting the appropriate filter. ### ✔️ Solution Offer a filter or a checkbox, maybe in the left panel, that makes it possible to filter out monitors that are up. ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:41:10 -05:00

closed this issue
added the
feature-request

A:status-page
labels

deekerman commented

2026-02-28 02:41:16 -05:00

Author

Owner

@wphostnl commented on GitHub (Mar 29, 2023):

Would be great to have this feature

@wphostnl commented on GitHub (Mar 29, 2023): Would be great to have this feature

deekerman commented

2026-02-28 02:41:16 -05:00

Author

Owner

@apokryff commented on GitHub (Mar 31, 2023):

It would be very convenient. Now I have 500+ sites being monitored. To display only fallen monitors, in the status page I use css override.

.monitor-list > .item:has(.bg-primary) {display: none;}

But still, all these monitors are rendered into markup, which is not very cool, because for the output I use a rather weak computer, which can find it difficult to render all the elements

@apokryff commented on GitHub (Mar 31, 2023): It would be very convenient. Now I have 500+ sites being monitored. To display only fallen monitors, in the status page I use css override. ```css .monitor-list > .item:has(.bg-primary) {display: none;} ``` But still, all these monitors are rendered into markup, which is not very cool, because for the output I use a rather weak computer, which can find it difficult to render all the elements

deekerman commented

2026-02-28 02:41:16 -05:00

Author

Owner

@Piste commented on GitHub (Mar 31, 2023):

in the status page I use css override.

oh I didn't think of this. I guess I could use greasemonkey too (?)

@Piste commented on GitHub (Mar 31, 2023): > in the status page I use css override. oh I didn't think of this. I guess I could use greasemonkey too (?)

deekerman commented

2026-02-28 02:41:16 -05:00

Author

Owner

@MaxPowers1337 commented on GitHub (Apr 3, 2023):

+1 :)

@MaxPowers1337 commented on GitHub (Apr 3, 2023): +1 :)

deekerman commented

2026-02-28 02:41:16 -05:00

Author

Owner

@ozgurerdogan commented on GitHub (Jun 2, 2023):

Well it is better to see them on top of list...

@ozgurerdogan commented on GitHub (Jun 2, 2023): Well it is better to see them on top of list...

deekerman commented

2026-02-28 02:41:16 -05:00

Author

Owner

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

This issue seems very similar to #1585 which has an open PR (#1971).

@Piste if you agree, please close this issue or edit the issue to make it more distinct ^^
(duplicates don't help to make the ammount of issues more manageable)

@MaxPowers1337 @ozgurerdogan @wordpresshosters
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 3, 2023): This issue seems very similar to #1585 which has an open PR (#1971). @Piste if you agree, please close this issue or edit the issue to make it more distinct ^^ (duplicates don't help to make the ammount of issues more manageable) @MaxPowers1337 @ozgurerdogan @wordpresshosters 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:41:16 -05:00

Author

Owner

@Piste commented on GitHub (Jun 4, 2023):

Thanks for the pointer, @CommanderStorm. Super helpful.
Closing in favor of https://github.com/louislam/uptime-kuma/issues/1585

@Piste commented on GitHub (Jun 4, 2023): Thanks for the pointer, @CommanderStorm. Super helpful. Closing in favor of https://github.com/louislam/uptime-kuma/issues/1585