mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Alternative to issue history #2013
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#2013
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 @Appoxo on GitHub (Mar 18, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
Ability to change the view of historical issues. Currently there is only a list of
✔️ Solution
A github like activity overview for daily/weekly/monthly/yearly for downtime (the grey dark/light green grid).

A live example for example for Reddit: https://www.redditstatus.com/uptime
This would make it more readable and create a better understanding how often a service was not responsive
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (May 25, 2023):
@Appoxo is this a duplicate of #1984?
If not, please make this issue less similar by editing your issue.
@Appoxo commented on GitHub (May 25, 2023):
Can be considered a duplicate. Thank you :)
@CommanderStorm commented on GitHub (May 25, 2023):
Could you then please close this issue? ^^
@CommanderStorm commented on GitHub (Jun 11, 2023):
Thanks ❤️