mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
improve status page #2214
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#2214
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 @enzofoucaud on GitHub (May 26, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
It would be nice to improve the status page to look something like this.
Example:
https://status.multiversx.com/
https://status.multiversx.com/uptime
✔️ Solution
Improved UX + added API info?
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (May 26, 2023):
Why? What is better?
Please edit your Issue to be more specific.
Also note that some features of atlasian (subscribtion, kalendar display options, mutli-step-incidents) are tracked in other issues. Creating duplicate isssues is creatates more work for everybody
@enzofoucaud commented on GitHub (May 31, 2023):
Yes, sorry, I could have been more specific in my request.
What I like about Atlassian is the little extra details, such as uptime over the last X days, info on why you've lost connections by moving your mouse over the various points, see past incidents at the bottom of the page, add a uptime page, etc
@CommanderStorm commented on GitHub (May 31, 2023):
Please open one feature request per feature request and do a duplication search for each of them. (for example for the detialed incidents, see the duplicates mentioned in #1253)
Like you wrote the issue, this is not manageable, given the number of issues.
Furthermore, please be more specific about why you want this feature and why this information would be important for you.
@shdf2 commented on GitHub (Jun 1, 2023):
Sorry to hijack this request :)
in the status page, what about displaying a detailed view when we click on a monitor. Actualy when we click on a monitor nothing happens, so we could have the detailed view like in the dahsboard, when we are logged in.
This shouldn't be hard to implement as the pages already exists.
in case I'm not clear, I'm talking about this view (of course without the buttons edit/delete etc...)
@CommanderStorm commented on GitHub (Jun 1, 2023):
@shdf2
Please open another issue. Like this, this is indeed unmanagable.
Also, please run a duplication search, there may be issues which are very close.
@CommanderStorm commented on GitHub (Jun 13, 2023):
@enzofoucaud
Like you wrote the issue, submitting non-detailed
feature-requeststhis is not manageable, given the number of issues.Could you close this issue and reopen single-issue
feature-reuqestsinstead? (only you or Louis can close this issue)@CommanderStorm commented on GitHub (Jun 13, 2023):
❤️