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

# Opening the Event Viewer window

### Introduction

The Event Viewer window lists the activity on your site; event messages and alarm messages.

### Procedure

1. Click **Monitor** from the menu bar.
2. Click **Event Viewer**.

### Result

The Event Viewer window displays:

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

**Notes:**

* If you have a mouse with a scroll wheel, it is possible to scroll (up or down) one event at a time, providing the scroll bar appears at the side of the Event Viewer window.
* When the Event Viewer is resized or moved, it will remember its size and position, even if Command Centre is closed and re-opened.

### Hints

{% hint style="info" %}
**New activity**

The Event Viewer window updates dynamically; when new activity occurs, the appropriate alarm or event message is displayed at the top of the window.
{% endhint %}

{% hint style="info" %}
**Old activity**

The Command Centre system has a limit as to how many messages are displayed, (i.e. 500 events). However, generating an Activity report will enable you to view older activity that has occurred.
{% endhint %}


---

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