> 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/multi-server-systems/event-aggregation.md).

# Event Aggregation

### Introduction

In a multi-server environment, event aggregation allows remote server events to be aggregated on the local server. This allows for centralized reporting and provides a central location for event backup and data maintenance purposes.

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

**Note:** The events that are displayed to an operator will depend on the operator’s privileges.

#### Network Disconnection

If an event aggregation server is offline, remote server events will be aggregated at the earliest time possible upon restoration of the device. The Status and Overrides tab of a Remote Server item indicates the number of events waiting to be aggregated.

#### Archived Events

Remote server events that have been archived and deleted will not be aggregated to the local server. Only events in the remote event database are available for aggregation.

In 'Star' structured multi-server systems:

* Child servers can receive/view local events only.
* The parent server can receive events from all child servers.
* A child server cannot aggregate events from the parent server or other child servers.
* Once a server becomes a child serverm it must log off and log back in again. Otherwise the child server can still see the events from other servers just like the parent server.

### Before you begin

* You will need to have a multi-server environment installed and configured before enabling event aggregation.
* All servers must be on the same build of Command Centre. All servers must be on Command Centre vEL7.10 or later.
* You will need to nominate a server that will receive events from the remote server(s). This nominated server is referred to as an event aggregation server. Any number of servers can be nominated as event aggregation servers. An event aggregation server will receive events from all remote server(s) that have been configured to aggregate events (via the **Setup** tab of each remote server).

### Procedure

To enable event aggregation, perform the following procedure on the event aggregation server:

1. Click **Configure** from the menu bar, then **Services & Workstations**.

   The **Services and Workstations** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Highlight the Remote Server you want to receive events from.
3. **Right click** and select **Properties**.
4. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-38e53ad6ef1939d547146c02f5b1b5fee8573edf%2Fremoteserver_setuptab.png?alt=media)
5. Check the **Receive all events from this remote server** checkbox.
6. The **From** date indicates the date that all events (that are not 'archived and deleted') will aggregate from.

   What events do you want aggregation to apply to?

   <table><thead><tr><th width="132">If...</th><th>then...</th></tr></thead><tbody><tr><td>past events,</td><td>set the date/time control to the required date in the past. This causes historical events to commence aggregation 'from this past time' forward.</td></tr><tr><td>all future events,</td><td><p>leave the date/time control as the current date.</p><p>All events 'from this current time forward' will commence aggregation.</p></td></tr></tbody></table>

   **Note:** The **From** date can only ever be applied as a current or past date. Setting the date in the future generates an error message.
7. To commence aggregation, click the **Apply** button.

#### Viewing the number of events waiting to be aggregated

To view the number of events waiting to be aggregated from the remote server, click the **Status and Overrides** tab of the Remote Server’s property pages.

When event aggregation is enabled, the following message displays in the **Status** field:

<table><thead><tr><th width="306">Message</th><th>Description</th></tr></thead><tbody><tr><td><em>"&#x3C;number> event(s) waiting to be aggregated."</em></td><td>This is the number of events on the remote server that have not yet been aggregated to the local server.</td></tr></tbody></table>

8. Repeat Steps 2 - 7 for each server you want to aggregate events for.

   **Note:** Event aggregation can be stopped at any time by unchecking the **Receive all events from this remote server** checkbox and applying the change. If re-enabled, no duplicate events will be aggregated.


---

# 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/multi-server-systems/event-aggregation.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.
