mirror of
https://github.com/DarkflameUniverse/DarkflameServer.git
synced 2026-10-02 10:53:44 +00:00
feat(dashboard): a simpler UGC card on Diagnostics
The card had the UGC page's counts per state for both kinds, totals since the server started and the last makes, which the UGC page's lists cover. It now says whether the UGC server is up (throttled, paused), how many items wait and failed (linking to the failed ones), its busy workers, CPU, memory and stored files. /api/diagnostics/ugc read the database on a worker thread; the counts are now read on the web thread and the worker only fetches the UGC server's status. Check: Diagnostics with the UGC server enabled: the card is short, reads right while it's up, throttled and stopped, and the failed link opens the failed ones. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -698,7 +698,9 @@ second of each server, HTTP requests per second of the dashboard and the UGC ser
|
||||
their request counts, errors and latency. **Live** shows the last 5 minutes at one second and updates as reports arrive
|
||||
(the `traffic` WebSocket topic); **1 hour** is at 10 seconds; **24 hours** (5 minutes) and **7 days** (30 minutes)
|
||||
come from the database. The servers table also shows each server's RakNet connections, average ping and resent
|
||||
messages, and the worker threads of the dashboard and the UGC server.
|
||||
messages, and the worker threads of the dashboard and the UGC server. While the UGC server is enabled, its card says
|
||||
whether it is up (throttled, paused), how many items wait and failed (a link to the failed ones), its busy workers, CPU,
|
||||
memory and stored files; what it made and how long each took is on the UGC page.
|
||||
|
||||
How it is counted:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user