Current Behavior
When visiting the dashboard (/), the panel makes around 50-75 separate HTTP requests (one request per server) to fetch server resource data (CPU, memory, disk, network, etc.).
Refreshing or navigating quickly can trigger the rate limiting feature, temporarily blocking the user.
This happens even without heavy interaction, just by staying on or reloading the dashboard.

As such, it only happens on panels with many servers.
Expected Behavior
The dashboard should fetch server resource data more efficiently, ideally in one batched request or using WebSockets.
Users should not hit the rate limit just by viewing the dashboard.
Server load should be minimized while keeping resource data reasonably up-to-date.
Steps to Reproduce
Refresh the page or navigate away and back within a short period.
Panel Version
1.12.0
Wings Version
1.12.1
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?
Current Behavior
When visiting the dashboard (/), the panel makes around 50-75 separate HTTP requests (one request per server) to fetch server resource data (CPU, memory, disk, network, etc.).
Refreshing or navigating quickly can trigger the rate limiting feature, temporarily blocking the user.
This happens even without heavy interaction, just by staying on or reloading the dashboard.
Expected Behavior
The dashboard should fetch server resource data more efficiently, ideally in one batched request or using WebSockets.
Users should not hit the rate limit just by viewing the dashboard.
Server load should be minimized while keeping resource data reasonably up-to-date.
Steps to Reproduce
Refresh the page or navigate away and back within a short period.
Panel Version
1.12.0
Wings Version
1.12.1
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
Is there an existing issue for this?