...
The VSphere discovery is designed ti discovery to discover physical servers (ESX) and their virtual servers. It will also get OS and their IP address, but only if the VMware tools are enabled and running on the virtual server.
The Synchronizer to VMware connexion is always through the VSphere server, and only need a read only access to it. The Shinken Enterprise servers do not ned need any direct access to the ESX servers.
The Shinken Enterprise to VSphere communication is done with the SOAP API from VMWare, onto a an HTTPS connexion.
Nagios or Shinken Framework configuration files
Shinken Enterprise is able to load any Nagios or Shinken Framework configuration files. It will automatically load the dfined defined objects into its configuration.
...
The network scan discovery is optional. It's done thanks to the nmap command, launched on the Synchronzier server. It allow allows to scan networks defined by the Shinken Enterprise administrators.
...
All discovered data from the Synchronizer are saved into a Mongodb database. It If possible, it's better for the database to be set aside the Synchronizer daemon. this database do not need to be shared with other daemons, and so its communications should be limited to the local synchronizer server.
...
The non-admon users will be restricted in the visibility onto the hosts that they are direct contacts linked to, or are in a contact group linked with the hosts.
This interface is using the save Mongodb dtabse databse than the synchronizer daemon. The default port for this configuration interface is 7766.
...
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 is if the otehrs others daemons are defined to use it.
...
This daemon is hosting the whole system configuration into memory. It have has access to all server names, address, types, and also the defined command used to check them.
...
| 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 a an arbiter slave, and only from the the master to theslavethe slave |
| Arbiter | Broker | 7772 | HTTPS |
The scheduler
...
The broker daemon exports and manages data from schedulers. The management can is be done exclusively with modules. Multiple broker modules can be enabled simultaneously. Example of broker modules:
...
The dispatch is a host-based one: that means that all services of a host will be in the same scheduler as this host. That means that the administrator does not need to know all relations among elements like parents, hostdependencies host dependencies or service dependencies: Shinken Enterprise is able to look at these relations and put these related elements into the same shard.
...