> For the complete documentation index, see [llms.txt](https://gsfcorp.gitbook.io/macula/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gsfcorp.gitbook.io/macula/administration-guide-v1.33.0/global-events.md).
# Global Events
Global events are alarms accessible from any server within the Macula Enterprise installation - unlike normal events, which are visible only from one particular server. There are no types for global events; they are simply system-wide alerts that can be used to make one server's events trigger actions from another server.
Each added global event will be available in the *Event & Action Configurator* of every server within the system, and will be accessible in two ways:
* in the *Events* section on the left: *Global event* event
* in the *Actions* section on the right: *Send global event* action
#### Add Global Events
To add global events via Macula Console, go to the *Events & Actions* section and choose *Global Events* from the menu on the left. Click the *+ New global event* button on the upper panel to bring up the configuration dialog box.
Enter an unambiguous **title** for the global event and click *OK* to save and exit the dialog box. The newly created event will appear in the item list and will become available for usage in the *Event & Action Configurator* on all connected servers.
Use the buttons on the upper panel to edit, deselect and remove global events; the filters on the bottom panel will help you load recently added or recently edited items.
#### Usage Example
Consider a system which has three servers, one of them central. Each of the 'slave' servers has a 'panic' button connected to the digital input of a camera. While each of the servers has its own local reaction for the 'panic' button configured, we also want the central server to keep the logs of 'panic' button press history.
The configuration for this use case might be as follows (local 'panic' actions omitted at this point):
* Server 1:
* Event 1: local 'panic' camera *digital input (DI)* activated
* Server 2:
* Event 2: local 'panic' camera *digital input (DI)* activated
* Central Server:
* Action 1: *Write to application log*, text: "Alarm button pressed on Server 1"
* Action 2: *Write to application log*, text: "Alarm button pressed on Server 2"
* Global events:
* *Global Panic 1*: 'panic' button pressed on server 1
* *Global Panic 2*: 'panic' button pressed on server 2
It does not matter which server global events are created on; they become visible on all servers after creation.
The **rules** for this configuration are as follows:
* Server 1:
* Event 1 triggers action *Panic 1: send global event*
* Server 2:
* Event 2 triggers action *Panic 2: send global event*
* Central Server:
* Global event *Global* *Panic 1* triggers *Action 1*
* Global event *Global* *Panic 2* triggers *Action 2*
The whole scheme is as follows when added to each server's configuration:
