System Monitoring
Vū Studio can show you the health of the Vū Media Servers you administer — whether each one is online, whether anything is wrong with it right now, and how much of the last 24 hours it has been reachable. The page that shows this is Fleet Health.
Fleet Health is a reporting page. Nothing on it casts, schedules, or changes anything on a system. If you want to see or change what is playing, that is the Display Dashboard →.
Where to Find the Dashboard
Fleet Health has no entry in the side navigation or on the Home screen. You reach it from a system's health badge on the Display Dashboard:
- Click the Vū Studio icon to go Home.
- Click Display Dashboard (also in the left side navigation) to open one.vu.studio/dashboard.
- On the header of any display node, click the coloured health badge next to the player name.
The badge is a link. It opens Fleet Health with that system's row highlighted, so you land on the one you were looking at rather than having to find it in the list.
You can also go straight to one.vu.studio/fleet-health (Home → Display Dashboard → health
badge) and bookmark it.
Who Can See It
Two things have to be true before Fleet Health shows you anything:
| Requirement | What it means |
|---|---|
| The Watchdog Dashboard feature is enabled for your account | System monitoring is enabled per account by Vū. Without it, opening the page sends you back to Home. |
| You are the registered admin of the system | You see only the Vū Media Servers where you are recorded as the admin — not systems you have merely connected to, and not systems administered by a teammate. |
If you expect to see a system and it is not listed, someone else is its registered admin. This is a deliberate limit of the first release, not a fault.
Being a member of a team that owns a system is not enough. A teammate of a system's admin sees nothing on this page until that admin's systems are shared, which is planned for a later release.
What the Dashboard Shows
The page has two parts: a summary row and a table.
The Summary Cards
| Card | What it counts |
|---|---|
| Walls | Every Vū Media Server you administer, healthy or not. |
| Needing attention | Systems in Degraded, Critical, Offline or Not reporting. |
| Offline now | Systems currently reported as disconnected. |
Needing attention deliberately excludes systems that have never reported anything. A system that has never sent data is unprovisioned, not failing. Those are counted separately, as N never reported, underneath the card.
The Table
| Column | What it shows |
|---|---|
| Wall | The system's name, with its ID underneath. The ID is what appears in logs and in support conversations. |
| State | The current status badge, with the reasons that produced it listed underneath. |
| 24h uptime | The share of the last 24 hours the system was online — see How the 24 Hour Uptime Number Works. |
| Reported | How long ago the status was last confirmed (just now, 12m ago, 3h ago), and the software version running on the system. |
Keeping Itself Up To Date
The page refreshes itself every 30 seconds — you never need to reload it. Under the heading it
shows Updated <time> · refreshes every 30s, so you can tell a live page from a tab that lost
its connection. Refreshing pauses while the browser tab is hidden and catches up when you come back
to it.
If you administer no systems at all, the page shows No walls to show instead of the table.
Reading the Status Badges
Each system shows one status badge. The same badge, with the same wording and colour, appears on the display node in the Display Dashboard.
| Badge | Colour | What it means | What to do |
|---|---|---|---|
| Healthy | Green | Everything being measured is within limits. | Nothing. |
| Degraded | Amber | Something is wrong, but the system is still working. | Read the reasons. Usually worth scheduling a fix rather than acting immediately. |
| Critical | Red | Something is broken now. The system may be showing nothing on the display. | Read the reasons and act. |
| Offline | Red | The system is reported as disconnected. | Machine, network, or power — check the room before the software. |
| Not reporting | Amber | Data was arriving and stopped more than five minutes ago. | The monitoring service or the machine has stopped. The last status is stale, so it is no longer shown. |
| Starting | Blue | The system is coming up. | Wait. This is not a fault. |
| Shutting down | Grey | The system is stopping on purpose. | Nothing. This is a planned stop. |
| No data | Grey | This system has never reported. | Monitoring is probably not enabled on it. |
Two rules decide which badge you see:
- Offline beats everything. A system's last health reading outlives the system itself, so a machine that stopped while healthy would otherwise keep claiming Healthy forever. When the system is reported as disconnected, that wins regardless of the last reading.
- A status older than five minutes is no longer shown as current. It becomes Not reporting instead. A live system is never more than about a minute behind, so anything older than that is out of date and is not presented as the truth.
Reading the Reasons
When a system is Degraded or Critical, the reasons appear under the badge as short codes. Red codes are Critical, amber ones are Degraded.
| Reason | Plain meaning |
|---|---|
VUOS_DOWN | The display process on the Vū Media Server is not running. The display is almost certainly showing nothing. |
SERVER_DOWN | The internal service that drives the system is not running, so the system cannot be controlled. |
LOCK_STALE | That internal service is still present but has stopped reporting in — hung rather than stopped. |
VUOS_NOT_RESPONDING | The display process is running but not answering. |
VUOS_WEBSOCKET_DEAD | The connection to the display process is gone, so commands cannot reach it. |
SERVER_CRASH_LOOP | The internal service has restarted repeatedly after errors. Usually a symptom of a frozen display process. |
DISK_FULL | Disk usage is at 97% or above. Playback and logging throw errors from here on. |
DISK_WRITE_CRITICAL | Sustained disk writes high enough to affect playback. |
THERMAL_THROTTLING | The machine is hot enough to be slowing itself down. |
MODE_FLAPPING | The system keeps switching between states. Treated as Critical because intermittent faults are easy to miss. |
DISK_HIGH | Disk usage is at 90% or above. Worth clearing before it becomes DISK_FULL. |
DISK_WRITE_HIGH | Disk writes are elevated. |
VUOS_MEMORY_HIGH | The display process's memory use keeps growing. A restart usually clears it. |
INTERNET_OFFLINE | The system has no internet. Local playback is usually fine; anything cloud-based is not. |
LATENCY_HIGH | Network round trip is over 250 ms. |
LATENCY_JITTER_HIGH | Latency is unstable, even where the average looks acceptable. |
SERVER_UNREACHABLE | The internal service is running but not answering on its port. |
ERRORS_HIGH | Five or more errors in the system's recent log. |
GPU_PROBE_FAILED | The GPU could not be read. |
Nothing appears the instant it goes wrong. The serious process reasons have to hold for ten seconds before they are reported, so an ordinary restart does not turn the page red.
How the 24 Hour Uptime Number Works
The 24h uptime column is the share of time a system was online out of the time it was actually being watched — not out of a flat 24 hours.
- A system first seen two hours ago reads
100.0% of 2h observed. It does not read8%, because the other 22 hours were never observed. - A system that has never reported reads
— never reported, not0%. No evidence of being down is not evidence of being down. - Once a system has been observed for the full window, the qualifier disappears and you see a plain percentage.
Health Badges on the Display Dashboard
Every display node on the Display Dashboard (one.vu.studio/dashboard — Home → Display Dashboard) carries the same health badge, with the same words and colours as Fleet Health, next to the player name. Clicking it opens Fleet Health with that system's row highlighted.
Two details are worth knowing:
- No badge at all means there is nothing to report to you — you are not that system's registered admin, so its health is not yours to see. That is different from a grey No data badge, which means the system is yours and has never reported.
- The dot on the left of the node header is a different thing. That dot is player connectivity: it tells you the player is connected. A player can be connected while the machine around it is degraded, which is exactly why both indicators exist.
Limitations
The first release of system monitoring is deliberately narrow:
- Only the registered admin of a system sees it. A teammate of that admin sees nothing.
- The Watchdog Dashboard feature must be enabled for your account. Without it the page is not available and opening its URL returns you to Home.
- No history. The page shows the current state and a 24 hour uptime figure. Per-system event history and charts are not part of this release.
- It reports what is wrong, not why it happened. It can tell you an internal service stopped; it cannot yet tell a fault from a deliberate restart.
- Nothing here can restart or control a system. Fleet Health reports only. Use the Display Dashboard → and Remote Restart → for actions.