The Broker daemon provides access to Shinken internal data. Its role is to get data from schedulers (like status and logs) and manage them. The management is done by modules. Many different modules exists : export to graphite, export to syslog, export into ndo database (MySQL and Oracle backend), service-perfdata export, couchdb export and more. To configure modules, consult the broker module definitions.
The Broker definition is optional.
Variables in red are required, while those in black are optional. However, you need to supply at least one optional variable in each definition for it to be of much use.
define broker{ | |
broker_name | broker_name |
address | dns name of ip address |
port | port |
spare | //[0/1]// |
realm | realm name |
manage_sub_realms | [0,1] |
modules | modules |
} |
define broker{
broker_name broker-1
address node1.mydomain
port 7772
spare 0
realm All
## Optional
manage_arbiters 1
manage_sub_realms 1
timeout 3 ; Ping timeout
data_timeout 120 ; Data send timeout
max_check_attempts 3 ; If ping fails N or more, then the node is dead
check_interval 60 ; Ping node every minutes manage_sub_realms 1
modules livestatus,simple-log,webui
}