mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Show timeline for a period of days #2359
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#2359
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 @dsvinovacaogp on GitHub (Jul 10, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
When adding a new "status page" or modifying it, give the option to show the timeline for a specific period, like 24 hours, 7 days, 15, 30 or even 90 days as the atlassian status feature provides. The status page pattern has shown a short period per minute or hours and in many cases for us it is bad. It could include an option to leave this configuration optional and customize the timeline by period.
Example:
Openai status for a period of 90 days.
Status OpenAi
✔️ Solution
Have an option in the configuration menu of a status page to configure the visualization of a timeline for periods of hours or days of up to 90 days.
❓ Alternatives
Last case, is there a way to set it to a minimum of 24 hours?
📝 Additional Context
No response
@CommanderStorm commented on GitHub (Jul 10, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/3264
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? ^^
@dsvinovacaogp commented on GitHub (Jul 10, 2023):
No problem, I haven't really encountered this feature before. Closing. Grateful.
privacy-respecting usage metrics? #3101