RoomScene 3D
Download

Zabbix in 3D: putting problems where the hardware is

Zabbix tells you that a power supply failed on PO-SRV-04. It does not tell you that the server is in rack A07 at U21, behind the CRAC unit. This is how to close that gap, with or without a dedicated tool.

Published

What Zabbix maps do, and what they leave out

Zabbix network maps are built for topology. You place host icons on a canvas, draw links between them and let each icon change colour with its problems. For a WAN, a core network or a signal chain that is often enough.

A map is still a hand-drawn 2D picture. You can upload a floor plan as the background and drop host icons on top of it, and some teams do. But the map has no idea what a room, a rack or a U is. It does not know that two hosts share a rack, that a frame occupies 4U, or that the next free 2U is at A09 U12. Every move means someone edits the map by hand, and in a busy equipment room that person is rarely the one doing the move.

So when a trigger fires at 03:00, the on-call engineer reads the host name, opens a spreadsheet or a Visio elevation of uncertain age, and goes looking. A physical view fixes that only if it is generated from data, not drawn.

Mapping hosts to physical positions

The core of any physical view is one record per device with a position: site, room, rack, U and height. The Zabbix host is linked to that record. There are three common places to keep the position:

  • In Zabbix itself. Host inventory has location fields, and host tags can carry values such as room:CAR-1, rack:A07, u:21. Cheap to start, but nothing stops two hosts claiming the same U, and passive equipment never makes it in.
  • In a spreadsheet. The usual starting point. Fine for reading, poor at enforcing anything, and it drifts from Zabbix as hosts are added and renamed.
  • In an inventory that links to Zabbix. The position lives with the device record; the Zabbix host ID is one attribute of it. The inventory can then hold what Zabbix never will: patch panels, KVM switches, passive splitters, blanking panels.

Whichever you pick, link by a stable key. Host names change when someone tidies up a naming convention; the host ID does not. Name matching is a good way to make the first links, not a good way to keep them.

Host groups are useful during that first pass. A group such as Playout servers or Network/Core narrows the list of candidates when you are placing devices into a rack, and it is a reasonable first guess at the device type. Do not treat groups as location: a host is usually in several groups, and none of them says where it is.

Colouring by worst open problem

Zabbix has six trigger severities. A physical view should use the same names and, ideally, the same colours, so nobody has to translate.

SeverityTypical useEffect on the view
Not classifiedTriggers nobody has graded yetShown, lowest priority
InformationEvents worth knowing, no actionUsually shown, often filtered out
WarningSomething to look at during the dayDevice coloured
AverageDegraded service, redundancy lostDevice coloured, counted on the rack
HighService at risk nowDevice, rack and room flagged
DisasterService downDevice, rack and room flagged

The rule that works is simple: a device takes the colour of its worst open problem. A rack takes the worst colour among its devices. A room takes the worst colour among its racks, plus a count. With that rollup a High on one power supply in A07 is visible from the site overview, before anyone opens the room.

A few details decide whether people trust the colours:

  • Disabled hosts and triggers. Leave their problems out. A host disabled for a hardware swap should not paint the rack red all week.
  • Maintenance. Zabbix can suppress problems during a maintenance period. Decide whether suppressed problems colour the device, and make the choice visible.
  • Acknowledged problems. They are still open. Most teams keep the colour and mark the acknowledgement on the device card.
  • Filtering. Severity counters that hide everything below High are what the night shift uses. Show the counts even when the filter hides the colours.
  • Stale data. If the last successful read from Zabbix was twenty minutes ago, say so. Green from a dead connection is worse than no colour.

A read-only connection

A visualization only needs to read hosts, host groups, problems and a handful of items. It should not be able to write anything. Since Zabbix 5.4 the API supports tokens, which avoids storing a user password in another system.

  1. Create a user role of type User and limit its API access to the methods the tool needs, if your Zabbix version allows it.
  2. Create a user group with Read permission on the host groups that should appear in the view, and nothing else.
  3. Create a dedicated user in that group with that role. Do not reuse a person's account.
  4. Generate an API token for that user, with an expiry date your security policy accepts.
  5. Test it: the number of hosts the token sees should match what you expect. A low count usually means a missing host group permission.

Power and temperature from the PDUs

Most metered PDUs and environment sensors are already in Zabbix through SNMP templates. Those items can drive a power and temperature view of the room, if you pick the right ones.

  • Units. Power items arrive in W or kW, temperature in °C. Normalise before you add anything up.
  • Totals versus phases. A three-phase PDU may report a total, per-phase values, or both. Use the total if there is one, otherwise sum the phases. Never add both, or the rack doubles.
  • What to ignore. Per-outlet readings, rated capacity and peak values are useful on their own but must not go into the rack sum.
  • Current only. Some PDUs report amps and nothing else. Volts times amps gives apparent power in VA, not real power in W. Label it as such.
  • A and B feeds. The rack load is the sum of both PDUs. Each feed must be able to carry that total alone, or losing one feed takes the rack down. As an example: two 16 A single-phase PDUs at 230 V are about 3.7 kVA each, so a rack drawing 2.4 kW is comfortable on either feed; one drawing 4.5 kW is not.
  • Temperature. Use inlet sensors at the front of the rack. Exhaust readings at the rear are much higher by design and set off false alarms on a heat map.

Reconciliation and the devices Zabbix cannot see

Once inventory and Zabbix are linked, two lists become possible, and both are worth reviewing every week:

  • Zabbix hosts with no inventory record. Something was added to monitoring but nobody recorded where it went. Often a virtual host, sometimes a server that arrived for a launch and was never documented.
  • Inventory devices with no Zabbix host. Either monitoring was forgotten, or the device cannot be monitored.

The second list needs a third state. A broadcast equipment room is full of gear with no management interface: passive patch panels, distribution amplifiers without SNMP, older frames, KVM extenders. Mark them as not monitorable. Otherwise they either look healthy, which is a lie, or sit on the missing list forever, which trains people to ignore it.

How RoomScene 3D does it

RoomScene 3D was built around this method. Each room is a 3D model drawn from the inventory, with every device at its U position. It connects to Zabbix with a read-only API token, links hosts by name when you start and leaves the rest in an unplaced list filtered by host group. Open problems colour the device in Zabbix severity colours, the rack glows with the worst of its devices, and the room list shows a count. Problems of disabled hosts and triggers are not shown. The details are on the Zabbix in 3D page.

PDU totals, or the sum of the phases where there is no total, are read every two minutes in W or kW, along with inlet and ambient temperature in °C. They feed the power and temperature heat maps and the A/B feed view. Reconciliation lists what Zabbix has and the inventory lacks, and the other way round, and equipment that cannot be monitored can be marked “not monitorable”. Devices that are not in Zabbix can use the built-in ping or TCP check instead.

If your equipment list is in Excel today, turning an Excel inventory into a 3D model covers the import. For the wider question of what a broadcast facility needs from infrastructure software, see DCIM for broadcast facilities, or the rack elevation page. The 30-day trial has every feature on; point it at a test Zabbix and one room.

Try it on your own rooms

RoomScene 3D is a 30-day trial with every feature on. Install it on a test server and import one room.

Download the 30-day trial Ask for a quote

contact@roomscene3d.com · tahirfeyzioglu@gmail.com