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

# Viewing alarm details

### Introduction

You may want to see more details about a particular alarm.

**Notes:**

* The "Edit Alarms" operator privilege is needed to Acknowledge or Process alarms, however operators without this privilege are still able to add comments in the 'Comments' field.
* In a multi-server system, when a remote server is off-line, a user will not be able to acknowledge the alarm and it will be marked as offlline if they attempt to do so. All other remote alarms from that remote server will appear as offline, read only and the user will not be able to process or enter details against them.

### Procedure

1. Click **Monitor** from the menu bar, then **Alarm Viewer**.

   The **Alarm Viewer** window opens.
2. Highlight the alarm message.
3. Either:

   * **Right click** and select **Properties**, or
   * **Double-click** the alarm.

   If an Alarm Instruction has been defined, the **Instructions** tab displays by default. If there is no Alarm Instruction defined however, the **General** tab displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b424c864f45c142c8cfe4fc9d3c300ab2515c18b%2Falarm_prop.png?alt=media)

   The Occurrence Time section of this window relates to Alarm Flooding (see [Alarm Flooding](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/alarm-flooding.md) for a description of what Alarm Flooding is and how to configure it). The following details are displayed:

   * the Date/Time of the **first** occurrence of an Alarm Flood,
   * the Date/Time of the **most recent** alarm,
   * number of **occurrences** (i.e. flood count) of an alarm.

   The **Escalation** field indicates the escalation state of the alarm. The states are:

   * Non-escalated
   * Escalated
   * Escalated. Acknowledge/process disallowed.

   The Escalation field updates dynamically. If you belong to an Operator Group that is not allowed to acknowledge or process escalated alarms, the **Acknowledge** and **Process** buttons become disabled as an alarm escalates.
4. Click the other tabs as necessary to view specific details relating to the alarm:

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-97334636c0bb81a436603cbb7f1bebfd8c7c15d7%2Ftab_gen.png?alt=media" alt=""></div>

   This tab provides general details (who, what, where) about the alarm. It also includes the 'Event Group' the alarm falls under, which is useful to know in case you wish to run an Activity Report to try to resolve the problem raised by the alarm.

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8ee2afb279c16dc766a94289ebc786c6c38b61e0%2Ftab_inst.png?alt=media" alt=""></div>

   This tab only appears on the Alarm Properties page if there is an [*alarm instruction*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#alarm-instruction) associated with the alarm. It displays the alarm instructions which you should follow before processing or acknowledging the alarm.

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c6e6d35039bacc508728ffa513cbd609634f40de%2Ftab_hist.png?alt=media" alt=""></div>

   All past actions regarding this alarm are displayed, (e.g. When an operator enters notes and acknowledges the alarm, this information will be entered into the **History** tab).

   An audit entry is also added to this tab every time an alarm is viewed, indicating which operator viewed it.

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-63547ef20015344ecf3c64e48d347c07cda93cd8%2Ftab_det.png?alt=media" alt=""></div>

   Additional details regarding this alarm are displayed, (e.g. the reason why the alarm occurred).

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-4b405039c39412c2db51bb32c606d986d3439a6e%2Ftab_images.png?alt=media" alt=""></div>

   This tab only appears on the Alarm Properties page if there is an image sequence associated with the alarm. It displays a grid of images. When one is selected the Sequence Viewer window is displayed.
5. The **Alarm Notes** field only displays if alarm notes have been configured in the system, on the **Alarm Notes** tab of the Server properties. Refer to [Alarm Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/alarm-notes.md) for further information.

   The title of this field displays as either **Alarm Notes (required)** or **Alarm Notes**. This indicates whether the operator needs to select alarm note(s) in order to process or acknowledge the alarm or not.

   When the Alarm Property window is closed, all the selected alarm notes and optional comments are saved. They can then be traced from the **History** tab.

   When the focus is set on the Alarm Property window, Alarm Notes can be selected via function keys. By default, < **F1** > to < **F8** > are assigned to match the first eight alarm notes.

   **Note:** If a function key that has no matching alarm note is pressed, then nothing happens.
6. The ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c1a6e386f72d3952c160c0384d6c2fd9e56caeab%2Fviewnextalarm.png?alt=media) checkbox allows you to step through the alarm queue and display each alarm when more than one is present. When it is checked the next alarm in sequence automatically pops-up after you have either acknowledged or processed an alarm, or you press the < **F12** > function key on your keyboard.

   The next Alarm Properties window will be that of the next in decreasing priority/time (as displayed in the Alarm Viewer window) if you are processing alarms from the Alarm Viewer, or if entered from the hardware item (either via the Hardware window or Site Plan) then it would further filter on the hardware item.

   **Note:** To use this feature you need the "Edit Alarms" operator privilege.
7. Click the buttons as required:

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-79de2628f4ce35bd0abc781f47a65d756fe2c7a6%2Fsiteplan.png?alt=media" alt=""></div>

   This button will be enabled if the site item for which the alarm has occurred is on a Site Plan. Clicking this button will display the relevant site plan indicating the site item.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2f693addb3a93d7ac192a9d8301d953d7f3c7133%2Facknowledge.png?alt=media) (or press the < **F10** > function key on your keyboard)

   This allows you to acknowledge an alarm so that any relays or alerts triggered by the alarm are reset. See [Acknowledging an alarm](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/acknowledging-an-alarm.md) for further detail.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d06d1743e311dbbd5cb7344952b476c1c8101d00%2Fprocess.png?alt=media) (or press the < **F11** > function key on your keyboard)

   This allows you to process an alarm once the alarm condition has been dealt with. See [Processing an alarm](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers/processing-an-alarm.md) for further detail.

   **Note:**

   The **Acknowledge** and **Process** buttons may be disabled for escalated alarms if you belong to an Operator Group that is not allowed to acknowledge or process escalated alarms (via the Operator Group **Configuration** tab).

   <div align="left"><img src="https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9d569033b10e60846beaa0deb2a16d6aced91034%2Fnextbutton.png?alt=media" alt=""></div>

   This button allows you to go to the properties of the next alarm without closing the Alarm Properties window. When there are no more alarms this window closes.
8. Click **Close**.

### Result

The Alarm Properties window closes.

You have viewed details about the alarm (or alarm flood), but taken no action.


---

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