What Sightline monitors

Sightline takes what your monitoring platform, your plant and your VMS already raise. A reading from the power chain, a fault reported by a server, a dry contact wired to a panel zone, a camera analytic and a door event from the access platform all arrive as the same kind of event. A failing fan tray and a forced door are then handled the same way by the same operator, on the same queue, and they end up on the same record.

The shape every event arrives in
  • The kind of event
  • The sensor, device or service that raised it
  • The group it belongs to, which is an area, a system or a customer account

That third field is what lets a plant event name the kit it affects. When a feed drops, the event already says what sits on it and who it serves.

Why it matters for an audit

Everything below arrives in that shape, whatever raised it. A failing fan tray and a forced door are the same kind of object on the queue, carry the same severity scale, take the same routing rules and end up on the same record.

Nothing on this page is a separate subsystem with its own console.

01

Power

  • UPS Load, runtime remaining, self-test results and bypass state
  • Standby batteries Whatever the UPS reports about its own batteries, pushed to us where it supports notifications and polled on a schedule where it does not
  • Generators and ATS Fuel, run hours, start failures and transfer events
  • PDUs and circuits Draw, phase balance, headroom and loss of redundancy
02

Cooling and environment

  • CRAC and chilled water Supply and return temperatures, compressor and fan state
  • Room conditions Rack-level temperature, humidity, pressure and airflow
  • Leak detection Rope and spot sensors pinned to their position on the floor
03

IT and IoT

  • Servers and hosts Health and power faults, as reported into the platform
  • Network Reachability and link faults, as reported into the platform
  • IoT sensors Anything that can close a contact or raise a panel zone
  • Time source faults Clock drift and time synchronisation failures, which turn up later as authentication and log correlation problems
04

Hazard

  • Gas and hazard detectors A hydrogen or off-gas detector in a battery room reaches us as a panel zone or a dry contact, and takes the same severity, routing and procedure as anything else on the queue
  • Thermal imaging Where a thermal camera watches a switchboard, its analytic arrives as a camera event, so a rising hotspot and the breaker alarms for that board sit next to each other on the same queue and in the same record
05

Life safety

  • Fire and suppression Detector state, release and abort, interlocks
  • Aspirating detection VESDA levels and faults
  • Dry contacts Any critical interlock a panel can present
06

Security

  • CCTV and video Live view and recorded footage attached to the event
  • Access control Door and reader activity, forced and held-open events
  • Cage and rack doors Open and closed state at cage and rack level, against the account that cabinet belongs to
  • Intrusion panels Panel and zone state, arm and disarm, test mode
How signals reach us today
  • Dry contact and volt-free, wired to an alarm panel zone
  • Alarm panels and diallers over Contact ID, SIA and IP receivers
  • Camera analytics raised through the VMS, such as line crossing or a person detected
  • Access control head-ends that report into the monitoring platform

This covers most of what actually gets escalated out of a hall, and it needs no new hardware on site.

On the roadmap
  • SNMP traps for network and power
  • BACnet/IP change-of-value for facility plant
  • Modbus TCP and RTU for facility plant
  • Redfish and IPMI for servers
  • ONVIF for cameras

These are direct reads that would bypass the monitoring platform. We have not built them yet, so we have listed them here rather than above.

Where Sightline stops, and what we take instead

Naming these is worth more to us than claiming them. Each one is a system that does its job better than we would, and in each case we take what it raises.

We do not calculate it
  • PUE and energy efficiency. Your DCIM or energy platform works it out. We take its threshold breaches and report which of them reached an operator and what was done
  • Capacity planning. Headroom before a breaker trips is DCIM's job. We handle the alarm when the headroom runs out
We do not instrument it
  • Access control hardware. Sightline works alongside OSDP-based access control. We take door and access events from the access platform, not from the reader bus
  • Battery monitoring. We do not put instrumentation on a battery string. If your site runs a dedicated battery monitoring system, its events arrive here like any other source and get the same procedure and the same record

Every direct protocol read listed as roadmap above is listed there because we have not built it. When it ships it moves up a column on this page, and not before.

Cameras, access control and alarm panels on the same queue

Environmental monitoring platforms stop at the plant. They will tell you a CRAC unit has failed and say nothing about the camera that went offline an hour earlier, or the badge that failed three times at the cage door at 02:00. Those are the same shift, the same operator and often the same incident, and they belong in the same queue.

Cameras

Live view and recorded footage appear alongside the event itself, so the operator can check the picture while staying in the procedure they are working through.

Access control

Door and reader activity raised as events in their own right, so an entry that should not have happened is handled like any other exception, with the same record at the end of it.

Intrusion and alarm panels

Panel state, zones and tests appear on the same surface as power and cooling, so an operator who is already working the queue does not have to open anything else to deal with them.

The Australian Government's February 2026 risk advisory for the Data Storage or Processing Sector notes that "even in a high security environment like that of data centres, malicious insiders have a level of access that could enable significant disruption."