mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Show uptiom #2845
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#2845
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 @fabry00 on GitHub (Nov 25, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
I'd like to have up to 1 year uptime statistics in the status page
So far I can see only the last 24 hours.
Is it possible to add a drop-down to select the period in the status page?
✔️ Solution
I'd like to choose the period of the metrics shown in the status page.
We could have a dropdown that can be used to select the time period (24 hours, week, month, year)
❓ Alternatives
No response
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Nov 25, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2477
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
@chakflying commented on GitHub (Nov 25, 2023):
Duplicate of #1667