mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
An actual dashboard page, showing multiple monitored devices #3056
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3056
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @aristosv on GitHub (Jan 20, 2024).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
We have 160 remote devices we're monitoring with ping. Playing around with .css I was able to show around 80 of them, by creating a 10x8 grid status page. But the boxes for each device are too big, and there's a lot of wasted space on the top of the page, showing the logo, a title, the "edit status page" and "go to dashboard" buttons, and the "services" title.
✔️ Solution
remove all content from status page and give the option to create grids and resize boxes. Use the whole page just for the monitored devices. We also use site24x7 and this feature is critical for creating monitoring dashboards and displaying then on large screens in the NOC. Dashboards are critical for efficient monitoring, this is what IT organizations are looking for, and it will take uptime kuma to the next level.
❓ Alternatives
provide the .css code by creating multiple templates, or implement a template system with various options for the status pages.
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jan 20, 2024):
Multi-column status pages are tracked in #592
I don't see a significant difference between these issues
If I am missing something, we can reopen this isssue ^^
=> closing as a duplicate
Note that our contribution guide is avaliable at https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md