mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Customizable autoRefreshInterval on Status Page #2140
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#2140
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 @rvsit on GitHub (Apr 25, 2023).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
With the countdown now added in #2878 it would be great if we could customize the
autoRefreshInterval(as seen on https://github.com/louislam/uptime-kuma/blob/master/src/pages/StatusPage.vue#L435).For my usecase I would like the dashboard to refresh every 30 seconds e.g.
✔️ Solution
Add the ability to customize the
autoRefreshIntervalin the sidebar when editing a status page.❓ Alternatives
A configuration variable would also be sufficient for my usecase
📝 Additional Context
I am willing to make a pull request if helpful, does not seem like it would be too difficult to implement
@chakflying commented on GitHub (Apr 25, 2023):
The response is still cached for 5 minutes server-side in
server\routers\status-page-router.js, that needs to be handled somehow.@rvsit commented on GitHub (Apr 26, 2023):
Did not catch that, thank you for that addition, that might indeed make it a little more difficult to make it customizable.
@asdf1nit commented on GitHub (May 15, 2023):
Vote for this.
@CommanderStorm commented on GitHub (Jul 27, 2023):
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/978#issuecomment-1362496508 (said issue is also more popular)
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?) ^^
@chakflying commented on GitHub (Dec 6, 2023):
Reopening to track this issue specifically here.
@brooksvb commented on GitHub (Dec 13, 2023):
We just set up Uptime Kuma for our IT team and everyone loves the tool. I did come across this issue though because we would like to have a shorter refresh interval. I'm glad the issue is already here and there has been recent activity. I hope to see this feature.