Vistigo Infra

Find the failing fan before the server does.

Switches, servers and power, read from the management controllers and the network itself. When something starts to go, it turns up in Slack with the rack, the device and the reading attached, while the spare power supply is still running.

noc.444.video/infra/rack-a04
Hosts up
142/142
PSU redundancy
1 lost
Hottest inlet
31 °C
Server 07, fan 4
0 rpm
Core uplinklast 24 h
DeviceRead byReadingState
core-sw-01SNMPGi1/0/48 at 78% outHIGH
server-07iDRACPSU 2 lostPSU
pdu-aSNMP v17.2 AOK
ups-01SNMP-NO DATA
Mock-upDrawn with sample data. Screenshots of the live infrastructure dashboards will replace it.
RackA04, 42U
PSU A / BOK / OK
Inlet24 °C
Load3.2 kW
Uplink78%
Problems1 warning
Example values

Where the numbers come from

Zabbix and Prometheus are trusted everywhere because they work. What usually goes wrong is the setup: templates nobody tuned and alerts nobody reads. That's the part we do.

Switches

Port throughput, errors, discards, optic levels, CPU, uptime and unexpected reboots

SNMPZabbix, vmagent

Every port and uplink, with an alarm on any reboot nobody asked for

VictoriaMetrics
Traffic between VLANs

Who's talking to whom, and how much

sFlow, NetFlowFlow collector

Sampled flows from the switch, turned into top talkers

VictoriaMetrics
Servers

Power supply status and redundancy, fan speeds, inlet and CPU temperatures, disk health

iDRAC, IPMI, SNMPZabbix

From the management controller, so it works even when the OS is down

Zabbix
Hosts and VMs

CPU, memory, disk space, network, whether services are running

Zabbix agent, node_exporterZabbix, Prometheus

Collected on site and held on disk if the uplink drops

VictoriaMetrics
PDUs, UPS and batteries

Load per outlet, runtime left, charge, watts in and out, temperature

SNMP, BluetoothTelegraf

Even a battery that only speaks Bluetooth gets a small gateway

InfluxDB
The easy-to-forget things

Certificates about to expire, clock drift, DHCP pools filling up, backups getting old

Agent, exportersZabbix, Prometheus

The quiet problems that cause the loud outages

Zabbix

Rooms, racks and what's in them

Grafana, in 444Video's house style

  • Overview
  • Server health
  • Network
  • Power
  • Problems

Alerts: tagged by severity and sent to Slack, email or your NOC, so the right person gets woken up.

What your team opens

One home page per room, rack or customer.

Start here

Overview

Every host, switch and power feed on one page, with problems sorted to the top.

Compute

Server health

Power supplies, fans and temperatures for each server.

Network

Network

Port throughput, errors, optics and the top talkers.

Power

Power

PDU load per outlet, UPS runtime and battery charge.

Who uses it

NOC and IT operations

One view across rooms and sites, and alerts you can trust.

Broadcast engineering

The servers and switches behind playout, next to the streams they carry.

Managed service providers

A view and alert routing for each customer, from one system.

Edge and remote sites

Unattended racks and flyaway kits, watched from anywhere.

10 racks to 3

for a UK multiplex operator, with remote monitoring replacing manual checks

About 70%

less space taken by kit on that project

Purple

is what no data looks like here. A silent device never passes for a healthy one.

Rack and footprint figures from the 444Video case study for a UK multiplex operator.

It all runs on the same system

Add another product whenever you like. The data lands in the same place, so a dropped stream and the satellite link it was on show up on the same timeline.

Tell us what you can't see.

Tell us what's in your racks and where they are. We'll show you what Vistigo would put on screen.