5.4.2 EventDB architecture and redundancy

Events and alarms are a basic concept of any monitoring system. They are used to inform operators about thinks happens in their environment. Our built-in event handling consist of different parts:

• Event are created from devices, users or from the backend processes
• All events are stored in the event database, by default for 1 year
• Access to the actual or historical events via Webclient or API
• Event notification Add-ons sending selected events to external entities (e.g. via E-Mail)

All events are "tagged" with the name of the source. This could be a built-in name or the name of an MNC service:

The name of an MNC service is configure by changing SATNMS_HOSTNAME in /etc/satnms.rc. Please use UPPERCASE letters for the name. No special characters or whitespaces are allows. More information about can be found in the chapter satnms.rc.

In simple stand-alone M&C systems the event database runs directly on the same server - just built-in - no addition configuration required. But all "event producers" in the system are designed to submit new events not only to the local EventDB but also to up to two destinations. This allows a fully redundant event database setup consisting of a main and backup database, without additional synchronization.

The following chapters describing some common setups.