> 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/processing-numerous-alarms.md).

# Processing numerous alarms

### Introduction

There are instances, (e.g. when setting up a new site), where a large number of alarms get into the system.

With the 'Advanced User' operator privilege, you can:

* process all inactive alarms in a Priority group, or
* process all alarms, both active and inactive, in a Priority Group.

With the "Bulk Process Alarms" operator privilege you can only process all the inactive alarms in a Priority Group. Refer to [Operator Privileges](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-privileges.md).

**Note:**

For escalated alarms you must belong to an Operator Group that is allowed to acknowledge or process escalated alarms (via the Operator Group **Configuration** tab) to have the "Process All" and "Force - Process All" functions available.

### Procedure

#### Process Inactive alarms in a Priority Group

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

   The **Alarm Viewer** window opens.
2. **Right click** on the alarm priority group header.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d4be7fd0d82b67881683c5708953ceedbfa09b2b%2Fhide_alm1.png?alt=media)
3. From the displayed pop-up menu, select **Process All**.

#### Process All Alarms in a Priority Group

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

   The **Alarm Viewer** window opens.
2. **Right click** on an alarm priority group header and press the **Shift** key at the same time.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d4be7fd0d82b67881683c5708953ceedbfa09b2b%2Fhide_alm1.png?alt=media)
3. Select **Force-Process All**.

### Result

An Alarm Notes dialog displays, regardless of whether or not the alarm notes feature is mandatory, if there are alarm notes configured.

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

If the alarm notes feature is mandatory, and the alarm group’s priority is greater than or equal to the minimum priority for alarm notes, then the title is set as **Alarm Notes (required)**, and the **Process** button is not enabled until you select at least one alarm note.

If the alarm notes feature is **not** mandatory, then the title is set as **Alarm Notes**, and the **Process** button is enabled.

If there are no alarm notes configured:

* the **Alarm Notes** grid is hidden,
* the **Comments** textbox expands to fill up the entire area, and
* the dialog is renamed **Command Centre**.

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

<table><thead><tr><th width="222">If you were processing...</th><th>then...</th></tr></thead><tbody><tr><td><strong>Inactive alarms</strong> in a Priority group</td><td>all the inactive alarms in that Priority group are processed and disappear from the Alarm Viewer window. Any active alarms, (i.e. alarms with a red bell icon), in that Priority group will still display.</td></tr><tr><td><strong>All Alarms</strong> in a Priority group</td><td>all alarms, (i.e. both active and inactive), in that Priority group, are processed and disappear from the Alarm Viewer window.</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 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/processing-numerous-alarms.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.
