-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As more 400 addresses were added, the list on the left disappeared. #2066
Comments
Unfortunately, it is too many for Uptime Kuma currently. I am thinking the monitor list have to be lazy loading in order to fix the issue. |
Some more related problems:
|
May I ask what 400+ monitors are for? Here a suggestion for a solution that might or might not work for you to avoid hitting this current limitation: You could separate/group your monitors and just run then multiple uptime-kuma docker instances. Just on different ports. So eg. you have total of 400 monitors, 100 are in LAN, 150 are websites, and another 150 are diverse… So it would be like this: ip.address:3001 = lan monitors Again, just a work around - not necessarily applicable in your situation, but maybe it is. Edit: oh i misread/ misunderstood your initial post… anyway; the above might be helpful for others. |
@chakflying you did not add this issue to #3515. Was this intentional? |
🛡️ Security Policy
Description
After adding around 1000 addresses to uptime Kuma, the sidebar disappeared (See the screenshot below).
👟 Reproduction steps
If you add more than 500 addresses, you probably encounter this problem.
👀 Expected behavior
Showing the right sidebar regardless of the number of Items added.
😓 Actual Behavior
The right sidebar becomes empty when too many addresses are added. The search field also disappears!
🐻 Uptime-Kuma Version
1.18.0
💻 Operating System and Arch
Ubuntu 22.04 64bit
🌐 Browser
Chrome, Edge, Firefox
🐋 Docker Version
Docker version 20.10.12, build 20.10.12-0ubuntu4
🟩 NodeJS Version
v16.16.0
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: