> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/understanding-the-alarm-viewers.md).

# Understanding the Alarm Viewers

### The windows

There are two alarm viewer windows available in Command Centre that can co-exist, (i.e. can both be opened on the same workstation). However, your operator privileges and what escalated alarm options have been configured will determine whether they are both accessible to you. They are:

* the main **Alarm Viewer**
* the **Escalated Alarm Viewer** (this window displays escalated alarms only, i.e. Alarms that have not been acknowledged within a specified time will display in the Escalated Alarm Viewer)

  **Note:** Escalation is set up via Action Plans.

The Alarm Viewer windows enable you to monitor alarms occurring at your site. The windows contain alarm messages only. However, these alarm messages are also included within the Event Viewer window.

The behaviour of both the main Alarm Viewer window and the Escalated Alarm Window can be configured via the Configuration tab of an [Operator Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#operator-group) properties. See [Changing the Alarm Viewer behaviour](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/changing-the-alarm-viewer-behaviour.md) for the procedure.

As the Escalated Alarm Viewer is essentially a filtered view of the main Alarm Viewer, both alarm viewers conform to the same behaviour as described in this chapter. Therefore, all the topics covered in this chapter relate to both Alarm Viewers.

**IMPORTANT:**

Where all operator configurations have been set to remove escalated alarms from the main Alarm Viewer, at least one operator must have the Escalated Alarm Viewer open at all times, to ensure escalated alarms remain viewable.

### Alarm Grouping

The alarms are grouped according to their priority level. When an alarm occurs, the alarm message displays at the top of the appropriate alarm group.

* The highest priority alarm grouping is displayed at the top of the window.
* The lowest priority alarm grouping is displayed at the bottom of the window.

### Alarm Flooding

Alarm flooding occurs when the same alarm is generated numerous times and fills up the Alarm Viewer window. Command Centre allows these alarms to be summarised by only displaying one instance of a flood alarm, with a flood count indicating the number of times the alarm has occurred.

### The alarm message

The alarm messages display in a summarised format (which messages are displayed to you will depend on your privilege level):

* what happened
* where it was generated
* who was concerned.

The date and time of the alarm message will flash until you acknowledge the alarm.

**Note:**

An online help file listing all the event/alarm messages can be accessed via the **Help** menu bar in Command Centre, and provides explanations of what each message means.

### Actions you can take

You can select an individual alarm message and view its details. From here, and with the correct privilege level, you can acknowledge and process the alarm.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/understanding-the-alarm-viewers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
