The Monitoring Gaps Behind a Green OT Dashboard

A dashboard showing a "normal" status is often taken as confirmation that everything is working as expected. In operational technology (OT) environments, however, a green indicator only reflects the signals the monitoring platform has been configured to evaluate.

Polling checks, heartbeat messages, and threshold-based alerts are useful indicators, but each has limitations that can affect how accurately a dashboard represents actual operating conditions.

Polling Intervals Create a Time Gap

Many monitoring systems collect at least part of their data at fixed intervals — every 30 seconds, every minute, or sometimes longer. Between polling cycles, the dashboard continues displaying the last recorded state.

For most conditions, this delay has little practical impact. During a fast-developing equipment fault, communication interruption, or sensor error, however, the situation can change before the next polling cycle updates the display.

The appropriate polling interval therefore depends on how quickly conditions can change and how soon the operations team needs to respond.

A Heartbeat Confirms Connectivity, Not Function

Heartbeat checks are commonly used to confirm whether a device remains connected to a monitoring platform. As long as the periodic signal arrives, the platform can continue marking the device as online or healthy.

A heartbeat confirms communication, but it does not verify that the device is performing its intended function correctly.

• A sensor can continue responding while producing inaccurate or frozen readings.

• A controller can remain connected while a downstream process has stopped.

• A gateway can respond normally while failing to transmit data from a connected device.

Because the communication path remains active, a basic heartbeat check alone will not identify these functional problems.

Thresholds Depend on How They Are Configured

Alert thresholds are intended to identify abnormal conditions before they develop into more serious issues. However, thresholds configured during initial deployment are not always reviewed as equipment, processes, and operating conditions change.

Thresholds set too broadly can miss early warning signs. Thresholds set too narrowly can generate excessive notifications and contribute to alert fatigue. Attempts to reduce this noise can then make meaningful conditions easier to overlook.

The important question is whether the thresholds still reflect current operating conditions and response priorities.

What This Means for OT Monitoring Design

These limitations do not make dashboards unreliable. They show why teams need to understand exactly what a "normal" status confirms — and what it does not.

For teams responsible for operational technology environments, three questions are worth asking:

• Would the polling interval catch a fast-developing fault before it escalates?

• Does a healthy status verify functional performance or only communication?

• Do current alert thresholds still reflect actual operating conditions?

A dashboard is only as meaningful as the signals and rules behind it. Reviewing those signals deliberately gives operations teams a stronger basis for decision-making than relying on status colors alone.