> For the complete documentation index, see [llms.txt](https://docs.tricloudnexus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tricloudnexus.io/management-portal/operations/alarms/standard-platform-alarms.md).

# Standard Platform Alarms

The monitoring system in the Nexus platform includes a predefined set of alarms that detect abnormal operating conditions across edge devices, system modules, and data connectors. These alarms serve as early indicators of potential failures, performance degradation, or configuration errors, enabling operators to identify and address issues proactively.

***

## Overview of Alarms

<table><thead><tr><th width="310">Alarm Name</th><th>Description</th></tr></thead><tbody><tr><td><strong>Data Connector State</strong></td><td>Raised when a data connector enters an error state or loses connection.</td></tr><tr><td><strong>Data Connector Endpoint State</strong></td><td>Indicates that the external system or endpoint associated with the connector is unreachable.</td></tr><tr><td><strong>Module Disconnected</strong></td><td>Triggers if a module fails to send heartbeat or telemetry for over 30 minutes.</td></tr><tr><td><strong>Module Configuration Alarm</strong></td><td>Raised when there are issues validating or applying configuration settings.</td></tr><tr><td><strong>Blob Storage Alarm</strong></td><td>Indicates issues with local blob storage, such as failed write operations or space limits.</td></tr><tr><td>Edge Agent <strong>Runtime Alarm</strong></td><td>Raised when the Edge Agent reports unhealthy status or runtime issues.</td></tr><tr><td><strong>Edge Hub Runtime Alarm</strong></td><td>Raised when the Edge Hub is non-operational or reports errors in message routing.</td></tr><tr><td><strong>Module Low Memory *)</strong></td><td>Triggered when a module's available memory falls below a defined threshold.</td></tr><tr><td><strong>Module High CPU *)</strong></td><td>Raised when a module consistently consumes high CPU resources.</td></tr><tr><td><strong>Device Low Disk Space Available *)</strong></td><td>Indicates that the device's available disk space is critically low.</td></tr><tr><td><strong>Module Communication Queue Size *)</strong></td><td>Warns of growing message queues within a module, indicating backpressure or downstream issues.</td></tr></tbody></table>

Certain alarms require that **Device Monitoring** functionality is active on the device. This is achieved by deploying the `DeviceMonitoring` module, which periodically collects health and performance metrics from both the host system and the deployed modules.

\*) Requires that the `DeviceMonitoring` module is deployed and running on the device.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tricloudnexus.io/management-portal/operations/alarms/standard-platform-alarms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.