starred/uptime-kuma

Fork 0

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

Have the option to make the status page show all monitors in columns next to each other instead of scrolling. #2712

New issue

Closed

opened 2026-02-28 03:04:26 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-28 03:04:26 -05:00

Owner

Originally created by @JackBZA on GitHub (Oct 24, 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

Would like to have the status page display the monitors in multiple columns in the browser instead of having to scroll up and down to view all the monitors. this would definably make uptimekuma a lot more usable for quick viewing/glancing.

✔️ Solution

Would like to have uptime kuma status page to give us an option to either disaply the status page in Lists or grid options with columns so all monitors can be displayed without having to scroll

❓ Alternatives

advise where i can edit the status page myself so I can rework the layout for my installation

📝 Additional Context

No response

Originally created by @JackBZA on GitHub (Oct 24, 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 Would like to have the status page display the monitors in multiple columns in the browser instead of having to scroll up and down to view all the monitors. this would definably make uptimekuma a lot more usable for quick viewing/glancing. ### ✔️ Solution Would like to have uptime kuma status page to give us an option to either disaply the status page in Lists or grid options with columns so all monitors can be displayed without having to scroll ### ❓ Alternatives advise where i can edit the status page myself so I can rework the layout for my installation ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:04:26 -05:00

closed this issue
added the
feature-request

A:status-page
labels

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 24, 2023):

I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1844 (which has duplicates like https://github.com/louislam/uptime-kuma/issues/2376 or https://github.com/louislam/uptime-kuma/issues/3062)
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

Note that our contribution guide can be found here and that we are open to contributions if you adhere to this

@CommanderStorm commented on GitHub (Oct 24, 2023): I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1844 (which has duplicates like https://github.com/louislam/uptime-kuma/issues/2376 or https://github.com/louislam/uptime-kuma/issues/3062) If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^ Note that [our contribution guide can be found here](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md) and that we are open to contributions if you adhere to this

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

@JackBZA commented on GitHub (Oct 24, 2023):

I think this is a duplicate of #1844 (which has duplicates like #2376 or #3062) If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^

Note that our contribution guide can be found here and that we are open to contributions if you adhere to this

I do not agree. I think this is different I will upload a picture that I made using paint of what I am aiming for :( just give me a second

@JackBZA commented on GitHub (Oct 24, 2023): > I think this is a duplicate of #1844 (which has duplicates like #2376 or #3062) If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^ > > Note that [our contribution guide can be found here](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md) and that we are open to contributions if you adhere to this I do not agree. I think this is different I will upload a picture that I made using paint of what I am aiming for :( just give me a second

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

@JackBZA commented on GitHub (Oct 27, 2023):

I would like it to look like this.

@JackBZA commented on GitHub (Oct 27, 2023): ![image](https://github.com/louislam/uptime-kuma/assets/148847929/4cbd02e9-a6fc-45bd-be48-9d2124d17144) I would like it to look like this.

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 27, 2023):

As noted above (I don't see a functual difference, only design):

If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?)

@CommanderStorm commented on GitHub (Oct 27, 2023): As noted above (I don't see a functual difference, only design): > If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?)

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

@JackBZA commented on GitHub (Nov 7, 2023):

As noted above (I don't see a functual difference, only design):

If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?)

I think that making it possible for people to select a grid layout like 2x2 or 4x4 or even have them manually adjust the layout by just adding the own grid options like 6x10 would be cool

@JackBZA commented on GitHub (Nov 7, 2023): > As noted above (I don't see a functual difference, only design): > > > If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) I think that making it possible for people to select a grid layout like 2x2 or 4x4 or even have them manually adjust the layout by just adding the own grid options like 6x10 would be cool

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

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

Referencing #4236 which did include a better mock up using the custom css feature

@CommanderStorm commented on GitHub (Dec 13, 2023): Referencing #4236 which did include a better mock up using the custom css feature

deekerman commented

2026-02-28 03:04:33 -05:00

Author

Owner

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