...
| Daemon | Listening Port | Protocol | Role |
|---|---|---|---|
| Synchronizer | 7765 | HTTPS | Manage the configuration |
| Arbiter | 7770 | HTTPS | Read and dispatch the configuration |
| Scheduler | 7768 | HTTPS | Manage monitoring logic |
| Poller | 7771 | HTTPS | Launch monitoring checks |
| Reactionner | 7769 | HTTPS | Launch notifications plugins |
| Receiver | 7773 | HTTPS | Receive external commands |
| Broker | 7772 | HTTPS | Get and export data |
The synchronizer
The synchronizer role
The synchronizer daemon manage the whole configuration. It use modules to detect new hosts and host modifications. It presents the configuration web interface to the administrators. Here are the optional sources the daemon can use to get information:
- Active directory
- VSphere (VMWare)
- Nagios configuration files
- Shinken framework configuration files
- Network scans
Active directory
The Active Directory discovery is done with a domain account, and only need read access. The connexion can be done in LDAPS to be sure the connexion is secure.
It is possible to define a top level OU in order to list only the elements (servers and users) that are defined below tis OU level.
The information that the module is getting are server names, FQDN, the server OS, and if defined in the LDAP entry, its locality.
The arbiter
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.
...