Too many signals, little operational clarity
SNMP, logs, and APIs generate data — but the shift does not know what to look at first or which device is truly at risk.
Otiumtek Iris · Operational observability
The platform
From secure access to the dashboard, inventory, and engine health. Tap any capture to enlarge.
How it works
Iris reads your devices over SNMP, normalizes telemetry, and shows what needs attention — with the monitoring engine itself under control.
Register devices with protocol, SNMP credentials, location, and autodiscovery when it applies.
Continuous read engine — scheduled cycles that keep status current without manual intervention.
Raw telemetry translated into operational states the shift can understand.
Patterns and grouped incidents — “no communication” on ten devices looks like one issue, not ten loose alerts.
Prioritized view: what needs action now, what is in warning, and what is still normal.
Iris monitors its own polling, metrics, and notifications — if the engine fails, you know before you go blind.
The pain you already know
Cameras and access depend on network and power. If nobody monitors that with operational criteria, the incident arrives late.
SNMP, logs, and APIs generate data — but the shift does not know what to look at first or which device is truly at risk.
A switch, UPS, or firewall offline affects cameras and access — and often no one sees it until the incident has already exploded.
IP spreadsheets, scattered SNMP credentials, and generic dashboards. No unified view of the estate and its real status.
> {name} exists so operations see infrastructure state — not a sea of SNMP numbers only IT understands.
For real operations
Iris is not a generic Grafana or a raw SNMP console. It is operational observability: inventory, polling, clear states, and a dashboard built for the team that responds when something fails.
Where it fits
{name} monitors switches, UPS, firewalls, and network via SNMP — the infrastructure that keeps cameras and access running. In the Suite it complements Onyx (data) and Tork (VMS events).
Business systems
sync and routing
Security platforms
Iris doesn’t replace the VMS — it watches the network and power infrastructure that keeps your security systems online.
In practice
From infrastructure NOC to a supervision dashboard — the same engine, different roles.
Monitoring of switches, UPS units, and the network that sustains cameras and access — clear states for the operations team.
Viewer user with dashboard-only access — without touching configuration or SNMP credentials.
Offline, no data, or active alarms — visible before it affects the VMS or field operations.
What exists, where it is, with which protocol, and under which status — not a stale Excel file.
Incidents grouped by theme — useful for support, equipment renewal, or stronger monitoring.
Onyx syncs data, Tork routes VMS events — Iris watches that the infrastructure underneath stays healthy.
The contrast
Without Otiumtek Iris
IP spreadsheets, manual SNMP queries, and dashboards nobody understands on shift. You learn about the problem when the camera already stopped streaming.
With Otiumtek Iris
Inventory, polling, and operational states in one panel — urgent first, with traceability and health of the monitoring engine itself.
Tell us which infrastructure you want to monitor — we assess inventory, SNMP protocols, and the dashboard your operation needs.
What happens next