# Monitoring device health This page provides insights into monitoring network, hardware and software-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 controller/module/processor-specific.

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

Status	Arrays / Modules	Controllers / Processors
🟢 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/Processors still function, but minor issues are observed. The show can go on, but it 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/Processors impacted, and major issues are observed. It should be checked as soon as possible.
🔴 Critical	Modules are severely compromised and might not make sound.	Controllers/Processors cannot function properly.
⚪️ Unknown	Modules are not reporting any information, or we cannot accurately report its health.	Controllers/Processors are not reporting any information, or we cannot accurately report their health.

{% hint style="info" %} The **Unknown** status is an addition to the health statuses used when the system cannot infer the accurate status of a specific device. An example of this is when a module or controller is offline. {% endhint %} *** ## Module's Health Each module component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device. * **Power status**—Power statuses have no effect on the module's health (e.g., a module can be asleep and still experience a network error). * **Network interfaces** * NTP * Ravenna and PTP (If Dante is selected as the AoIP protocol, these statuses will not be considered in the health status calculation). * **Hardware statuses** * Amplifiers * PSUs * Drivers

### Status calculation thresholds The all-arrays/system, individual array, and module's health statuses are derived from the aggregation of the different network and hardware statuses using the thresholds below:

Status	% of devices ≥ 🔴	% of devices ≥ 🟠	% of devices ≥ 🟡	% of devices ≥ ⚪️
🟢	–	–	–	–
🟡	1%	5%	5%	1%
🟠	10%	30%	–	30%
🔴	30%	50%	–	50%

#### Module's health The module's health is evaluated based on network and hardware statuses, which are derived from the aggregation of the criteria mentioned above. The highest severity level among these statuses determines the overall health of the module's network and hardware.

#### Single array's health The single array health is an aggregation of the hardware and network statuses of the modules inside a specific array. The highest severity of its components defines the health status shown in HOLOPLOT Control.

#### Arrays' health or system health The arrays' health is a single status derived from the health of all the system's arrays, using the thresholds mentioned above.

*** ## Controller's Health Calculating the health of controllers follows a similar approach to modules and arrays, although with different components and thresholds.

Each controller component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device. * **Online status** * **Network status** * **Connectivity** * HOLOPLOT Cloud * NTP * **Network** * Audio Module Control Network: It enables communication between the audio modules and the controllers for system management, operation, and configuration. * HOLOPLOT Control Network: It provides connectivity for HOLOPLOT Control and the Public System API, supporting user interaction and external system integration. * Audio Network: It supports Audio over IP monitoring services specifically for RAVENNA installations. It detects audio stream announcements and monitors audio streams to facilitate failover mechanisms. * Intercontroller Network: It facilitates the communication between HOLOPLOT controllers to synchronize their states and ensure redundancy in system operations. * **Hardware status** * Drives * Fans * PSUs

### Status calculation thresholds The controller health statuses are derived from the aggregation of the different network and hardware statuses using the thresholds below: Each module component group has its own logic and calculation approaches. Each outlined component state change generates an event for the respective device.

Status	% of devices ≥ 🔴	% of devices ≥ 🟠	% of devices ≥ 🟡	% of devices ≥ ⚪️
🟢	–	–	–	–
🟡	1%	10%	10%	1%
🟠	10%	30%	–	30%
🔴	50%	80%	–	50%

{% hint style="info" %} **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. To set up redundancy, go to **Settings** › **System Settings** and select your preferred setup. {% endhint %}

### CONTROL Status This status refers to the web browser's connection to the system, which is visible only in the footer.

*** ## Processor's Health

Calculating the health of processors follows the same status calculation thresholds as that of controllers, but considers one additional status category: software. * **Online status** * **Software status** * DSP: * DSP processing information * Beam and processor configuration status * Audio engine information * CPU Usage * **Network status** * **Connectivity** * HOLOPLOT Cloud * NTP * **Network interfaces** * **Audio Module Control Network**: It enables communication between the audio modules and the controllers for system management, operation, and configuration. * **Audio Bridge Network Interfaces**: * Audio Network: It supports Audio over IP monitoring services specifically for RAVENNA installations. It detects audio stream announcements and monitors audio streams to facilitate failover mechanisms. * PTP information. * **Hardware status** * Drives * Fans * PSUs #### Failover It provides information on which processor is used as the primary and backup device, ensuring that the OS can perform a Device Failover. This involves switching between two processors in a redundant pair, changing the state of an inactive processor to active, and vice versa. The failover status does not affect the overall health calculation of the processors. {% hint style="info" %} **Failover** To perform a Device Failover, a backup processor must be assigned beforehand. To set it up, go to **Settings** › **Processors** and select your preferred setup. {% endhint %}

*** ## Filtering and finding issues When navigating to the Device List, the right panel shows two collapsed cards: the filters and the issue tracker. They can be used together or independently.

### Filter The filter has two functions: When collapsed, it allows for monitoring of the Network and Hardware statuses.

When expanded, it allows for filtering based on Power, Network, and Hardware statuses, enabling the quick identification of system failures during debugging.

### Issue Tracker Whenever there's an issue affecting the network or hardware status, the specific issue will be displayed on the Issue Tracker in the following format `Type – Issue description.` Click the issue to filter the modules with that specific issue.