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

# Processing an alarm

### Introduction

After the alarm condition (what actually caused the alarm to be generated) has been dealt with, you can process the alarm.

**Note:**

The 'Edit Alarm' operator privilege is needed to Process an alarm, however operators without this privilege are still able to add comments in the 'Comments' field (limited to 1024 characters).

### 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.
4. If there is an **Instructions** tab displayed, perform the necessary action according to the alarm instruction before processing the alarm.
5. Select the appropriate **Alarm Note(s)**, and optionally enter details of what action you have taken in the **Comments** field.
6. Either:
   * Click the **Process** button, or
   * Press the < **F11** > function key on your keyboard.

### Result

The alarm message is removed from the Alarm Viewer window, but it remains within the Event Viewer window.


---

# 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-an-alarm.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.
