...
| 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 |
| Log Files | Distributed Monitoring (NOC Processor) [process_satellite.log] Distributed Monitoring (Satellite Processor) [send_status.log] Distributed Monitoring Event Log (NOC) [event.log] |
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.
...
- services
- hosts
- downtimes
- comments
- performance data
...
Status File Processing
The status file is automatically parsed and processed on the receiving system if it is a SONARPLEX.
Following actions are performed based on the received status file after it was compared with the last one:
- information update of existing hosts and services
- creation of new objects
- performance data update
- delete obsolete objects
Following are key features of the processing:
- object updates are executed through external commands (e.g. ADD_SVC_COMMENT, ACKNOWLEDGE_SVC_PROBLEM) during runtime
- check results are submitted as passive check results, which is an external command as well
- the monitoring configuration is updated if required
- the monitor process restarts if the configuration changed
- all configuration objects from the satellite are prefixed with its LOCATION_ID (see Configuration :: My Properties :: Resources)
Event Delivery
| Delivery Technologies | azeti Agent, SNMP Traps |
| 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 SONARPLEX to SNMP Trap Receiver (Northbound Integration) |
...