A wall screen nobody reads is furniture. A dashboard built around three questions — down, struggling, where — gets glanced at fifty times a day and pays for itself the first time it catches a link before the phones do.
OpManager arrives with dashboards, and like most defaults they show a bit of everything and answer nothing in particular. The fix is not more widgets; it is a stricter editor. A working office dashboard — and its big-screen sibling, the NOC view that rotates full-screen pages on a wall display — should answer three questions in under five seconds: is anything down right now, what is trending towards trouble, and where in the building or network is it. Everything that does not serve one of those questions is decoration, and decoration is what trains people to stop looking. This page builds the small set of widgets that earn their pixels, in the order a technician’s eye actually travels.
Layout example for one office. If a widget does not feed one of the three questions, it does not ship.
The top of the dashboard belongs to the availability summary: devices down now, interfaces down now, and the count of unacknowledged critical alarms. OpManager’s widgets cover device availability, alarm summaries and top-N devices by availability — assemble them as the first strip. The design rule is brutal and simple: on a healthy day this strip is green and boring, and any red in it names a device, not a statistic. A manager glancing from the doorway should be able to say “all up” or “the floor-two switch” without touching a mouse.
Below the down list goes the early-warning layer — the widgets that show tomorrow’s outage forming. Put the WAN interface utilisation graph here (from the WAN monitoring page in this series), plus the top-N lists OpManager offers for CPU, memory and disk usage across servers. These lists have a quiet second job: they are your capacity report. The file server that lives at 93 percent disk for a month is not an alarm — it is a purchase request writing itself, and it should be visible daily rather than discovered during a failure.
The third question — where — is answered by a map. OpManager’s network maps and business views let you lay devices over a floor plan or a simple site diagram, with live status colouring the icons. Build the view around how your office actually fails: core switch at the centre, floors or departments as clusters, the WAN link at the edge. When the floor-two cluster turns red behind one dead switch, the map explains in a glance what thirty alarms would take a paragraph to say — and it makes the dependency tuning from the alarm-storm page visible to everyone.
For a shared screen, assemble the dashboard into OpManager’s NOC view — the full-screen, auto-rotating display designed for exactly this. Keep each rotation page to one idea (status strip, WAN, map, server leaders), set a rotation slow enough to read, and mount the screen where the people who act on alarms actually sit — not in a corridor for visitors. A practical touch: use a small dedicated PC or stick that boots straight into the view, logged in with a read-only OpManager user. A wall screen with an admin session is a security incident waiting for a curious hand. Feature availability for NOC views and advanced dashboards varies by edition — check yours before promising the boss a wall.
Dashboards decay the same way monitoring does: devices are replaced, the WAN doubles in speed, the application everyone feared moves to the cloud — and the screen keeps lovingly graphing a decommissioned server. Put a fifteen-minute monthly review in the calendar: remove dead widgets, promote the device that caused last month’s pain, demote what has been green and irrelevant for a quarter. The test of the review is a new joiner: if they cannot explain the screen in their first week, the screen — not the joiner — needs work.
Dashboards are assembled from the same console the setup video tours — watch the walkthrough, then build your three-question version.
▶️ Watch Full VideoA dashboard is a page of widgets you open and use interactively. The NOC view is the presentation mode — full-screen pages that rotate automatically on a shared display, built for a wall screen in the IT room. Most offices build one good dashboard, then publish it as a NOC view.
One or two admins, through their own accounts — and the wall display itself should run a read-only user. Dashboards edited by everyone converge to the demo look within a month: everything present, nothing answered.
Yes — the same three-question dashboard as the team’s browser home page does most of the work. The wall adds ambient awareness; the discipline of choosing few, honest widgets is where the value actually lives.