Monitoring device health

This page provides insights into monitoring network and hardware-related statuses in the Device List section. Discover how to utilize these statuses for system configuration and maintenance purposes.

The Device List section allows you to monitor system statuses in real-time at various detail levels—system level, array level, or module specific.

Device List

Status Breakdown

For all statuses, HOLOPLOT Control represents the severity level in 4 statuses. Here is their meaning:

Status	Arrays / Modules	Controllers
🟢 OK	Everything is functioning correctly. Sound can be played without issues.	Everything is functioning correctly. Operation is normal.
🟡 Warning	Sound can be played, there might be minor issues that compromise the system’s performance. Show can go on, but should be checked later on.	Controllers still function, but minor issues are observed. Show can go on, but should be checked later on.
🟠 Error	Modules can still make sound, but with severe degradation to system’s performance. Should be checked as soon as possible.	Controllers functionality is impacted, major issues are observed. Should be checked as soon as possible.
🔴 Critical	Modules are severely compromised and might not make sound.	Controllers cannot function properly.
⚪️ Unknown	Modules are not reporting any information, or we cannot accurately report its health.	Controllers are not reporting any information, or we cannot accurately report its health.

The Unknown status is an addition to the health statuses used when the system cannot infer the accurate status of modules, arrays, or controllers. An example of this is when a module or controller is offline.

Which statuses are monitored?

Each module component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device.

• Network interfaces

• Ravenna and PTP (If Dante is selected as the AoIP protocol, these statuses will not be considered in the health status calculation).

• NTP

• Power status

• Amplifiers

• PSUs

• Drivers

• SubLink

• Hardware states

All Status Monitored

Thresholds

For some aggregated states, HOLOPLOT OS 2.0 uses thresholds to calculate the derived health state, e.g., arrays health. The highest severity of its components defines the health status shown in HOLOPLOT Control.

Module's health

Module Health

The module's health is derived from aggregating all the above statuses. The highest severity of these statuses defines the module's health.

Single array's health

Single Array Health

The array health is derived from all its modules' health using the thresholds below

Status	% of Modules ≥ Critical	% of Modules ≥ Error	% of Modules ≥ Warning	% of Modules ≥ Unknown
OK	–	–	–	–
Warning	1%	5%	5%	1%
Error	10%	30%	–	30%
Critical	30%	50%	–	50%

Arrays' health or system health

System / Arrays' Health in the footer

Arrays' health is derived from all arrays' health using the thresholds below

Status	% of Arrays ≥ Critical	% of Arrays ≥ Error	% of Arrays ≥ Warning	% of Arrays ≥ Unknown
OK	–	–	–	–
Warning	1%	5%	5%	1%
Error	10%	30%	–	30%
Critical	30%	50%	–	50%

Controller's health

Calculating the health of controllers follows a similar approach to modules and arrays, although with different components and thresholds.

Controllers' health

In the case of an array of controllers, we use the following thresholds to display its aggregated health:

Status	% of Controllers ≥ Critical	% of Controllers ≥ Error	% of Controllers ≥ Warning	% of Controllers ≥ Unknown
OK	–	–	–	–
Warning	1%	10%	10%	1%
Error	10%	30%	–	30%
Critical	50%	80%	–	50%

Redundancy toggle An additional system setting informs whether modules and controllers are expected to have redundant network connections—Primary and secondary or just primary. This information affects how modules and controllers calculate their health.

CONTROL Status

This status refers to the web browser connection to the system.

CONTROL Status in the footer

---

Filtering

When navigating to the Device List, the right panel displays the filters by default. This section serves two functions:

1. Allowing for simultaneous monitoring of multiple statuses.

2. Filtering based on selected components and status type to quickly identify system failures during debugging.

Filtering errors on the Device List