AV monitoring & operations
Every AV installation is already documented in a spreadsheet — devices, rooms, IP addresses, switch ports. MonoLog reads that list and turns it into a live system: real-time status, alerts, full history and reports, building by building and room by room.
Runs on your own server No cloud account required Windows service or desktop app
The problem
Everything is in there: every device, every room, every address. And it is all dead knowledge — accurate the day it was written, silent every day after. Nothing in that file tells you that the projector in the auditorium stopped answering twenty minutes ago.
A device list records what was installed. It cannot tell you what is running right now, and it quietly goes out of date from the day it is handed over.
A failed ping says an address is unreachable. It does not say which room just lost its display, who is responsible for it, or what else went down at the same moment.
Your inventory becomes the structure — buildings, floors, rooms, devices — and live status flows into it. One system answers both questions.
How it works
Point MonoLog at the Excel list you already maintain. Buildings, floors, rooms, devices, IP addresses, VLANs, switch and patch-panel ports come across in one pass — including devices with several network ports.
Devices report their own status over UDP, MonoLog pings every documented address, and device drivers read real telemetry where they exist — lamp hours, temperatures, inputs, signal presence.
Alerts reach the people who need them, related alerts are grouped into one incident, notes stay with the device, and every report is one click and one print away.
What you get
UDP self-reports, ICMP ping and driver telemetry collapse into one honest status model: online, warning, offline, unknown — and every card says which channel the answer came from.
The installation in the shape it really has: buildings grouped into campus folders, rooms by floor, devices by room — plus photos so people recognise what they are looking at.
One alert per device, correlated into a shared incident with a root-cause candidate when several fail together. Notifications by email, Microsoft Teams or webhook.
Every event, filterable by building, room, device and category, with a long-term archive — and each line marked as reported by the device or observed by MonoLog itself.
Availability per room, mean time to recovery, a reliability heatmap, devices that keep flapping, outstanding maintenance — as one complete, print-ready document.
Where a driver exists: power, input, volume and routing straight from the browser — and Room ON/OFF as one ordered sequence across every device in the room.
LAN scanner to find what is actually on the network, a ping manager for everything else, and switch, port and VLAN documentation per network interface.
Four roles from administrator to read-only, device credentials encrypted at rest, HTTPS out of the box, and a licence tied to the installation — not to a cloud account.
Screens
No client to install. Shown here with a demonstration installation.
Deployment
MonoLog is installed inside the building it monitors. AV control networks are often isolated by design — so nothing here depends on an internet connection, an external database or a per-device subscription.
A planning companion for AV integrators is in preparation.
Demo
Send a short message and we will arrange a walkthrough — ideally against a real device list, so you see your own installation rather than a demonstration one.