> 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/alarm-list.md).

# Alarm List

The Alarms page helps operators and system administrators quickly identify active issues, assess their impact, and take corrective actions.

***

### Alarms List

The **Alarms** list in the Nexus Platform provides a real-time overview of all *standing alarms -* that is, alarms that are currently active or have returned to normal but have not yet been acknowledged.

<figure><img src="/files/zbKM8zgUSbj955y4rYnd" alt=""><figcaption><p>Screenshot from Alarms in the Nexus Platform</p></figcaption></figure>

***

### Layout and Functionality

The interface is structured as a sortable table with interactive controls that enhance usability and filtering. Each row in the table represents a single alarm instance with core information visible at a glance.

Alarms can be expanded to reveal additional metadata and context.

<figure><img src="/files/wQeUKxaf5GKe5QTV4nyB" alt=""><figcaption><p>Expanded alarm, where additional properties are visible</p></figcaption></figure>

***

### Toolbar Actions

The toolbar above the table includes several utility buttons:

<figure><img src="/files/b1DVj1DeLSylOPGo31iw" alt=""><figcaption><p>Alarm user interface buttons</p></figcaption></figure>

<table><thead><tr><th width="132">Button</th><th>Function</th></tr></thead><tbody><tr><td><p><strong>Acknowledge</strong></p><p><strong>Alarm</strong></p></td><td>Selecting one or more alarms enables the "Acknowledge Alarm" button. This acknowledges the alarms, indicating that the operator is aware of the condition and has taken responsibility for addressing it. Upon acknowledgment, the alarms are enriched with the operator’s name and the timestamp of the action. The operator may also include an optional comment to provide context, describe the intended mitigation, or document observations related to the alarm.</td></tr><tr><td><p><strong>Suppress</strong></p><p><strong>Alarms</strong></p></td><td>Allows selected alarms to be temporarily hidden from the view. Useful during maintenance windows or known transient conditions. Suppressed alarms are not deleted and will reappear once suppression ends. The suppression of alarms is based on logical filters.</td></tr><tr><td><p><strong>Reset</strong></p><p><strong>View</strong></p></td><td>Clears all filters, sorting, and expanded rows to restore the default table layout.</td></tr><tr><td><p><strong>Alarms</strong></p><p><strong>History</strong></p></td><td>Opens a historical view of all alarm state changes. This view includes alarms that are no longer standing but may be relevant for audit or troubleshooting.</td></tr><tr><td><strong>Refresh</strong></td><td>Manually refreshes the alarm list to fetch the latest state.</td></tr></tbody></table>


---

# 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/alarm-list.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.