mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
URLs not showing in uptime dashboard #3626
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#3626
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 @renugamanimegalai on GitHub (Sep 26, 2024).
📑 I have found these related issues/pull requests
We have 90+ URLs in uptime , when we open the dashboard it is taking more than 45 minutes to list all the
urls .
🛡️ Security Policy
Description
No response
👟 Reproduction steps
Add 40+ URLs
👀 Expected behavior
home page should load
😓 Actual Behavior
home page taking more time load
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
ubuntu 24
🌐 Browser
chrome
🖥️ Deployment Environment
📝 Relevant log output
No response
@tifirifi commented on GitHub (Sep 26, 2024):
Hi,
The issue you mentioned is known and will be addressed in the upcoming 2.0 release of Uptime Kuma. Version 2.0 is focused on improving performance, especially for larger numbers of monitors. You can track the progress or contribute here: GitHub Issue #4500.
For now, try reducing monitor history retention, increasing check intervals, or pausing less essential monitors to mitigate performance issues.
@CommanderStorm commented on GitHub (Sep 26, 2024):
My bet would be that https://github.com/louislam/uptime-kuma/pull/5025 resolved this issue and have marked said PR as such.
Said PR needs a review though