...
| source | Destination | Port | Protocol | Note |
|---|---|---|---|---|
| Poller | Scheduler | 7768 | HTTPS |
The reactionner
Role
The reactionner daemon issues notifications and launches event_handlers. This centralizes communication channels with external systems in order to simplify SMTP authorizations or RSS feed sources (only one for all hosts/services). There can be many reactionners for load-balancing and spare roles
Connexions with other daemons
The reactionner get it's configuration from the Arbiter daemon, on its 7769 port.
The configuration is the realm scheduler list where the reactionner will have to connect.
Mail server visibility
The reactionner launch notification plugins in order to notify contacts from host or checks alerts. Notification plugins are mainly based on the mail system, and so the reactionner server need a local MTA configured to relay emails to the contacts. The MTA configuration is up to the administrators.
Data
The reactionner get command from the schedulers.
It do not known about contacts. It only get commands to execute, and the commands are created by the schedulers.
Reactionner connexion summary
| Source | Destination | Port | Protocol | Note |
|---|---|---|---|---|
| Reactionner | Schedulers | 7768 | HTTPS |
The broker
The broker daemon exports and manages data from schedulers. The management can be done exclusively with modules. Multiple broker modules can be enabled simultaneously. Example of broker modules:
...