> 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/command-centre-client/using-command-centre/working-with-viewers/event-viewer/viewing-historical-events.md).

# Viewing Historical Events

This procedure describes how to refine the event list to view historical events:

1. Change the viewing mode from the default setting of **Live Events** to **Historical Events**.

   Date and Time fields, a **Filters** button and **Search** button display.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-e5fb65aef40302d358e3d3fc81e64071063741ed%2Feventviewer_historicalevents.png?alt=media)
2. Select a date time range, (i.e. **From** and **To** dates and times).
3. Click the **Search** button.

   You can further filter out irrelevant data from the events list, as follows:

   * Use ' **Event Filters** ' option to filter events by **Event Source** (Any/Specific event source(s)) and/or **Event Group or Type** (Any/Specific)
   * Use the ' **Cardholder Filter** ' option to filter events by **Specific Cardholder(s)** OR,
   * Use both ' **Event Filters** ' and ' **Cardholder Filter** ' to filter your data.

<details>

<summary>Event Filters</summary>

1. Click the **Event Filters** button.

   The Event Search Filters pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-02881434e699b22421e5d1e0aee63a5c8c33e020%2Feventviewer_searchfilterspopup.png?alt=media)
2. Select the appropriate **Event Source** from the drop-down list, (i.e. either 'Any' or 'Specific').

   If you select 'Specific', the **Specific Event Source or Related Items** button is enabled, allowing you to select the item(s) you require.
3. Select the appropriate **Event Group or Type** from the drop-down list, (i.e. either 'Any' or 'Specific').

   If you select 'Specific', the **Specific Event Groups and Types** button is enabled, allowing you to select those you require.
4. Click the **Close** button.

   The Event Search Filters pop-up closes and the event list is populated with events that fit the filter criteria.

   A message displays, along with a **Clear** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-939388f04fff18d651f3d82cac9c3f44da9584bb%2Feventviewer_livefilters.png?alt=media)

   **Note:** This message acts as a warning that any applied filters will persist until you click the **Clear** button.

</details>

<details>

<summary>Cardholder Filter</summary>

1. Click the **Cardholder Filter** button.

   The Cardholder Search Filter pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-0151c133aabd863bee7615e296dca5d34519f983%2Fcardholderfilter-cardholdersearchfilter.png?alt=media)
2. Select **Specific Cardholder(s)** from the drop-down list.

   The Select Cardholders button is enabled.
3. Click the **Select Cardholders** button.

   The Select Cardholders pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-4282590ed2df6fcd449a33720cac15b180cd9620%2Fselectcardholders_popup.png?alt=media)
4. Select what criteria you want to search on from the **By** drop-down list, (i.e. Name, Description, Division, Card Number or All). By default, Name is selected.

   In this procedure, the Name option is used.
5. Enter the Cardholder’s name in the **Search** field.

   A minimum of 3 characters starts the search.

   **Notes:**

   * When the search returns multiple Cardholders, double-click on the appropriate Cardholder to select.
   * Command Centre automatically selects the Cardholder when there is only one Cardholder matching the searched characters.

   Click the **OK**, then click **Close**.

   A message displays, along with a **Clear** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-939388f04fff18d651f3d82cac9c3f44da9584bb%2Feventviewer_livefilters.png?alt=media)

   **Note:** This message acts as a warning that any applied filters will persist until you click the **Clear** button.

</details>


---

# 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/command-centre-client/using-command-centre/working-with-viewers/event-viewer/viewing-historical-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.
