> 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/licensable-features/perimeter-fence-controllers/monitoring-fence-alarms-and-events.md).

# Monitoring Fence Alarms and Events

### Introduction

Monitoring fence alarms and events can be done from either:

* the Command Centre **Alarm or Event window**, or
* a **Site Plan**

  **Note:** Only alarms can be monitored from a Site Plan, (i.e. events cannot be), and the procedure for this method is already described in [Viewing Alarms from Site Plans](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/site-plans/viewing-alarms-from-site-plans.md).

You can acknowledge alarms using the existing alarm acceptance capabilities in Command Centre.

### Before you begin

Before you begin this procedure:

* Ensure that the Fence Zone has been assigned to a Fence Controller and has an Alarm Zone, and that the Fence Controller and Alarm Zone have been assigned to a Gallagher Controller 6000 or 7000.
* You need to be in the same or parent Division of the Division holding the Fence Zone, and have the "View Alarms" operator privilege to perform this procedure.

### Procedure

1. Open either the **Alarm Viewer** window or the **Event Viewer** window, by clicking **Monitor** from the menu bar, and then either:
   * **Alarm Viewer**, OR
   * **Event Viewer**
2. Highlight the activity message.
3. Either:
   * **Right click** and select **Properties**, or
   * **Double-click** the alarm/event.

The Alarm or Event Properties screen displays, providing more details.

**Note:** The alarm can be acknowledged and/or processed if you have the "Edit Alarms" operator privilege. If you do not have this privilege, you can still add comments to the 'Notes' field.


---

# 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/licensable-features/perimeter-fence-controllers/monitoring-fence-alarms-and-events.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.
