Skip to main content
Dashboards

Set Up the TV View for Live Fleet Status

Put your fleet's warnings, critical issues and offline servers on a full-screen board with octoja's TV View — open it, filter it, and set its alert sounds.

The TV View puts active check issues on online devices and offline servers on one full-screen board — built to run unattended on a wall display or spare monitor so your team catches issues at a glance. Colour-coded tiles sit above a live table of matching warnings, critical issues and offline servers; new problems flash as they arrive and can play an alert sound, and the board refreshes on its own without anyone touching it. This guide shows how to open the TV View, filter what it shows, and set up its alert sounds.

The TV View with status tiles, sound control, and a live table of current warnings, critical checks, and offline devices.

Before you start

  • The TV View permission is granted per group under Administration → Groups, in the Reporting area of the permission editor. Read lets the group open the board; Read & write also lets it change the board's settings, including the alert sounds.
  • The board shows the customers and devices you already have access to, so what appears follows your normal group scope.

Open the TV View

  1. Go to the Dashboard.
  2. Select TV View. The board takes over the whole window, without the usual sidebar and menus.
  3. On a wall display, choose Fullscreen in the board's header so it fills the screen edge to edge. Exit fullscreen brings the browser's own controls back.

Across the top, three tiles summarise the issues matching your active filters and access:

TileWhat it counts
Servers offlineServers that are currently not reporting in.
WarningsChecks currently in a warning state.
Critical checksChecks currently in a critical state.

Below the tiles, a table lists the matching issues with their Severity, Time, Customer, Site, Device, Type, OS and Check, newest first. A newly-arrived issue flashes briefly in its severity colour so a glance at the board catches what just changed, and clicking a row opens that device on its Checks tab. The board refreshes itself every 30 seconds, and the header, tiles and paging stay pinned while the list scrolls. When nothing matches, the board shows All clear.

The board shows unacknowledged active check issues only on online devices. When a server goes offline, its previous warnings and critical check results disappear from the board; an offline issue appears instead. Offline workstations and network devices do not appear. A check issue disappearing therefore does not establish recovery. Open the device's Checks tab to investigate its full status and history.

The tiles count all matching issues within your access and active filters, before the list limit is applied. For example, selecting only Critical makes Warnings and Servers offline show zero; this says nothing about issues hidden by the filter. Devices in maintenance are excluded when No maintenance is enabled. Both views use at most the 500 most recent matching issues — not 500 devices — and show a notice when there are more. Narrow the selection with OS and role filters; customer filtering and search are also available in Devices view.

Use the column picker to show Alias as well, so you can recognize devices by their assigned names. Clicking a table row respects your profile preference for opening devices in a new tab. Ctrl/Cmd-click or middle-click also opens a device in a new tab, leaving the board in place.

Choose checks or devices

The View toggle in the board's header decides how the list below the tiles is built. It is one choice or the other — the board is never in both views at once.

ViewLists
ChecksOne row per visible issue, as described above. The board opens in this view.
DevicesOne card per device with a visible issue, showing the highest severity and check issues among that device's visible issues.

Device cards use the alias when one is set, otherwise the device name. This lets the wall display use the names your team recognizes.

Pick Devices for a screen that should show which machines need attention rather than every single issue — a server with six failing checks becomes one card instead of six rows. Use the search field and customer filter to narrow the cards. These two filters apply only in Devices view; switching to Checks does not apply them. In More actions, choose sorting by Severity, Newest first, Device name, or Customer; this is not saved in the URL. Group by customer splits the board into customer sections with a device count and severity summary. Customer sorting then comes first (alphabetical by default), followed by your remaining sorting within each group.

Each card is a link to the device's Checks tab. You can open it in a new tab through the browser context menu or Ctrl-/Cmd-click. A normal click follows your preference for opening devices in a new tab.

Filter what the board shows

Enable No maintenance (wrench icon) to hide devices in maintenance mode from both the counters and the issue list. It is off by default. The choice is stored in the URL as maintenance=hide, so a bookmark preserves it. Changing this filter does not itself trigger sounds or flashing for existing issues that reappear.

The severity filter in the board's header holds one toggle per severity:

ToggleShows
CriticalChecks currently in a critical state.
WarningChecks currently in a warning state.
OfflineServers that are currently not reporting in.

The toggles add up rather than replace each other, so Critical and Offline together give you a board that ignores warnings. Choosing a selected toggle again clears it, and with none of the three selected the board shows everything.

To narrow the board further, use the Type filter — on the Type column header in the checks view, and behind the funnel button in the devices view. It holds two sets of toggles — OS (Windows, Linux, macOS) and Role (Server, Workstation, Network) — so one screen can watch, for example, only your Windows servers.

Every filter you set travels in the page address. Once a board shows what a screen should watch, bookmark that address and open it on the display: it comes back filtered the same way.

Turn alert sounds on

The TV View can play a sound the moment a new problem appears, so an unattended board gets attention even when no one is looking at it.

  1. On the board, choose Sound off in the header. It switches to Sound on.
  2. Browsers block audio until someone interacts with the page, so if the button reads Click to enable, click it once to allow sound.
  3. Choose the button again to silence the board at any time.

By default a built-in sound plays when an issue turns critical — a new one, or an existing one that has just escalated — and another when a server goes offline. Leave the sounds untouched to use those defaults.

The board only sounds for issues the current filter shows, so a screen with only Critical selected stays quiet when a server drops off.

Use your own alert sounds

With Read & write on TV View you can replace the built-in sounds with your own — changing them here changes them for everyone who opens the board.

  1. Open TV view settings from the gear button in the board's header. The button appears only for the groups allowed to change the settings.
  2. Under Critical issue, drop an audio file or click to browse. Do the same under Server offline for the offline sound.
  3. Use Play preview to hear a sound. Once a card carries a sound of your own, Reset to default puts the built-in one back.
  4. Choose Save. Nothing changes on the board until you do — Cancel drops what you picked.

Each file must be MP3, WAV, or OGG and at most 1 MB. Leave a slot empty to keep using the built-in default for it.

Tips

  • Put a shared wall-display login in a group whose TV View access is Read, and keep Read & write for the people who should change the sounds — that way a public board can't be reconfigured from the screen it runs on.
  • The board is designed to run for days on its own: it refreshes continuously and reconnects by itself, so you can leave it up without signing back in.
  • Point each screen at the OS or role it should watch, so a wall board stays readable instead of listing every issue in the fleet.