Introduction
The azeti Distributed Monitoring (DM) Technology is a key feature of the azeti SONARPLEX. Its application area is the monitoring of multiple remote sites (following called “Sattelite”) where the overall status is collected in one central SONARPLEX (following called “NOC”).
The so called NOC receives status information from its satellites and sub-satellites on regular base where alerts from one remote location are sent immediately to the NOC SONARPLEX. This allows you to monitor locations worldwide but having one central view, e.g. for your Network Operation Center. Each satellite schedules and executes checks locally and sends the results to one central destination.
The distributed monitoring uses two concepts for delivering information to the NOC. Both include different data and are scheduled differently.
Status File Delivery
| Delivery Technology | azeti Agent |
| Scheduling | regularly every n minutes |
| Data Content | overall status and monitoring configuration |
| Example Setup | SONARPLEX to SONARPLEX SONARPLEX to azeti Agent |
The status file delivery is a regularly scheduled job where the overall status of the satellite is delivered to the configured destination, the NOC. The delivery interval can be configured as well as the destnation.
A status file includes all necessary monitoring configuration informations as well as a snapshot of the overall status for all configured services and hosts. besides this acknowledgements, downtimes, contacts and all other necessary monitoring information is included. This overall status is generated right before the delivery to the NOC and is of course only a snapshot for this very moment.
New status information is interpreted by the NOC and required for the following tasks (all happen on NOC side):
- initial creation of objects
- update changed objects
- add new objects
- delete missing objects
The file includes information for the following objects:
- services
- hosts
- downtimes
- comments
- performance data
See the full list of supported events.
Event Delivery
| Delivery Technologies | azeti Agent |
| Scheduling | on every occurrence of an event |
| Data Content | Event information. See List of Events for detailed information |
| Example Architectures | SONARPLEX to SONARPLEX SONARPLEX to azeti Agent |
The second concept is the Event Delivery. Every new event is immediately delivered, after it was processed internally, to the configured destinations. It depends on the delivery technology how the event is processed on the NOC side.
Supported Architectures
Below are some distributed monitoring use cases explained which show how the delivery technologies can be used
Example Architecture
Below is an example scenario for monitoring of worldwide distributed locations where every location can also have a sub location. All status information and alerts and collected in "Central Office".
Each SONARPLEX communicates with the remote devices through the azeti Agent, which is installed on the devices by default. To save bandwidth and system performance, static information ( is sent regularly and updates are done incremental.