# Alarms

An **alarm** in the Nexus platform represents a system-detected condition that requires attention. Alarms are raised by the Device Monitoring component in the Nexus platform, when anomalies are detected. For example when monitored values exceed defined thresholds, communication fails, or system errors occur. Alarms are persistent entities with rich metadata to support tracking, filtering, and resolution across the entire platform.

Each alarm includes a set of core properties that uniquely identify it, describe its origin, and determine its importance. These properties also defines the *state* of the alarm—those are covered in the separate Alarm Lifecycle section.

<figure><img src="/files/tdSEJ0PcdPyVAssEMbpU" alt=""><figcaption><p>Alarms can be found in the Monitoring section of the main menu</p></figcaption></figure>

***

## Alarm Properties

<table><thead><tr><th width="153">Property</th><th>Description</th></tr></thead><tbody><tr><td><strong>Id</strong></td><td><p>A globally unique identifier for the alarm, also used as a human-readable name. This format ensures that alarms are uniquely traceable across distributed systems.</p><p>It is structured as:</p><p><code>{device id}.{property}</code></p></td></tr><tr><td><strong>Area</strong></td><td>A logical grouping that describes the source context of the alarm. Typically set to <code>Device</code>, but can also represent broader scopes such as a customer, system group, or hierarchical structure.</td></tr><tr><td><strong>TimeOn</strong></td><td>The UTC timestamp when the alarm was first triggered (entered the alarm state). This marks the beginning of the current alarm incident.</td></tr><tr><td><strong>TimeOff</strong></td><td>The UTC timestamp when the alarm condition returned to normal. If this value is <code>null</code>, the alarm is still active.</td></tr><tr><td><strong>Source</strong></td><td>Indicates the component type where the alarm originated. This could be a module on an edge device, a data connector, or a backend service.</td></tr><tr><td><strong>SourceReference</strong></td><td><p>A detailed path to the specific origin of the alarm. For example:<code>{management endpoint name}/{device id}/{module id}</code></p><p>This reference is used for correlation and root-cause analysis.</p></td></tr><tr><td><strong>Priority</strong></td><td>A numeric indicator of the alarm's severity. Lower values indicate higher criticality (e.g., 1 = critical, 999 = low priority). Priority helps operators sort and triage alarms based on operational impact.</td></tr></tbody></table>

These properties enable precise filtering, auditing, and escalation, ensuring that each alarm is actionable and traceable within its operational context.


---

# Agent Instructions: 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.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.