> 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/event-viewer.md).

# Event Viewer

### Introduction

The Event Viewer window enables you to view events and alarms occurring at your site.

Everything that occurs in the system, from "site configuration changes" to "overrides" to "cardholder changes", is recorded as an activity on the event log. As new activity occurs the appropriate message is displayed at the top of the window.

The event and alarm messages are displayed 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
* When it happened and when it was logged
* The type of event

You can select an individual message and view the details about the activity. From here, and with the correct privilege level, you can also acknowledge and process alarms.

If you want to see all operator events/workstation events associated with a cardholder you need to place the workstation into a division that you have the "View Events" operator privilege for.

**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.

***

### Scrolling through the Event Viewer

When scrolling through the Event Viewer window while new events are arriving, the Event Viewer window behaves as follows:

* If no events are selected then the Event Viewer window will return to the top when a new event arrives.
* If an event is selected then the Event Viewer window will keep its position, and will allow an operator to scroll back through the events in the window.
* If the selected event scrolls off the bottom of the Event Viewer window then it will be de-selected, causing the Event Viewer window to start showing the most recent events again.
* A selected event can be de-selected by clicking on it. Do this if you want to start displaying the most recent events again.

***

Select the item below that you require further detail on:

(Refer to [Operator Privileges](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-privileges.md) to check you have the correct operator privilege level for the activity you wish to perform.)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Opening the Event Viewer window](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/event-viewer/opening-the-event-viewer-window.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Viewing event details](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/event-viewer/viewing-event-details.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Events with Restorals](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/event-viewer/events-with-restorals.md)


---

# 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/event-viewer.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.
