0xfurai / 0xfurai/peekaping

[Feature Request] Monitor grouping and reordering feature

未關閉
#240 0 則留言 3 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
Go
星號
1.2k
分支
69
PR 合併指標
30 天內沒有已合併 PR

描述

**Is your feature request related to a problem? Please describe.**
On the status page, all monitors are currently displayed in a fixed order. This makes it difficult to highlight or prioritize the most important monitors at the top. In larger environments, this can reduce clarity, as less relevant monitors may push critical ones further down.

**Describe the solution you'd like**
Add a feature to **create groups** and **reorder monitors** on the status page.
Users could, for example, organize monitors into groups like *Network Services*, *Web Applications*, or *Internal Systems*, and define in which order both groups and individual monitors are displayed.

**Describe alternatives you've considered**
An alternative would be sorting monitors by name or using tags to simulate grouping, but this approach lacks flexibility and does not provide visual structure.
A more user-friendly option would be **drag-and-drop reordering** in the UI, similar to how Uptime Kuma handles it.

**Additional context**
Grouping and reordering monitors would make the status page significantly more organized and easier to navigate — especially for setups with a large number of monitors.
This would improve accessibility and help critical systems stand out more clearly.
Example reference: Uptime Kuma allows rearranging monitors directly within the dashboard using drag and drop.

Best regards
Phil

貢獻指南

這個儲存庫沒有索引到貢獻指南

研究方向

The status page rendering logic is likely in the frontend, possibly using a framework like React or Vue, and the monitor data comes from a Go backend API. Start by finding the API endpoint that serves the monitor list and the frontend component that renders the status page grid. Look for existing UI components that handle lists or grids to understand how to add drag-and-drop. 'Done' means users can create groups, reorder monitors via drag-and-drop, and the order persists.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
go
領域
backend-api-design, frontend
Issue 類型
功能
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
描述清楚
新手友好度
45/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。