Role
The arbiter daemon reads the configuration from the synchronizer. It divides it into parts (N schedulers = N parts), and distributes them to the appropriate Shinken Enterprise daemons. Additionally, it manages the high availability features: if a particular daemon dies, it re-routes the configuration managed by this failed daemon to the configured spare. Finally, it receives input from users or passive check results and routes them to the appropriate daemon. Passive check results are forwarded to the Scheduler responsible for the check. There can only be one active arbiter with other arbiters acting as hot standby spares in the architecture.
Connexion with the synchronizer
The communication between the arbiter and the synchronizer is done on the standard port of the synchronizer (7765).
Connexion with the other daemons
This daemon is used to check and dispatch configuration to the others daemons, but not the Synchronizer. The connexion is done on the standard port of the others daemons, and will use a HTTPS connexion if the others daemons are defined to use it.
Data
This daemon is hosting the whole system configuration into memory. It has access to all server names, address, types, and also the defined command used to check them.
It also host in memory the defined contacts that should receive notification for the defined hosts and services.
Arbiter connexion summary
| Source daemon | Destination | Port | Protocol | Note |
|---|---|---|---|---|
| Arbiter | Synchronizer | 7765 | HTTPS | |
| Arbiter | Scheduler | 7768 | HTTPS | |
| Arbiter | Poller | 7771 | HTTPS | |
| Arbiter | Reactionner | 7769 | HTTPS | |
| Arbiter | Receiver | 7773 | HTTPS | |
| Arbiter | Arbiter | 7770 | HTTPS | Only if there is an arbiter slave, and only from the the master to the slave |
| Arbiter | Broker | 7772 | HTTPS |