Page History

#===============================================================================
# BROKER
#===============================================================================
# Description: The broker is responsible for:
# - Exporting centralized logs of all Shinken daemon processes
# - Exporting status data
# - Exporting performance data
# - Exposing Shinken APIs:
#   - Status data
#   - Performance data
#   - Command interface
#===============================================================================

define broker {

    #======== Daemon name and address =========
    # Daemon name. Must be unique
    broker_name               broker-1

    # IP/fqdn of this daemon (note: you MUST change it by the real ip/fqdn of this server)
    address                   node1.mydomain

    # Port (HTTP/HTTPS) exposed by this daemon
    port                      7772

    # 0 = use HTTP, 1 = use HTTPS
    use_ssl Shinken Enterprise. Lines added by import core. Do not remove it, it's used by Shinken Enterprise to update your objects if you re-import them.
    _SE_UUID            core-broker-060340145ade11e5b703080027f08538
    _SE_UUID_HASH       8e00136f9e61061e07ca0f4a63509b68
# End of Shinken Enterprise part

    #======== Daemon name and address =========
    # Daemon name. Must be unique
    broker_name               broker-master

    # IP/fqdn of this daemon (note: you MUST change it by the real ip/fqdn of this server)
    address                   localhost

    # Port (HTTP/HTTPS) exposed by this daemon
    port  0


    #======== Master or spare selection =========
              # 17772

 = is a spare,# 0 = isuse notHTTP, a1 spare
= use HTTPS
  spare   use_ssl	                  0


    #======== DaemonMaster connectionor timeout and down state limitspare selection =========
    # timeout: how many seconds to consider1 = is a spare, 0 = is not a nodespare
 don't answer
  spare  timeout                   30


    # data_timeout: how many second to consider a configuration transfert to be failed
    # because the network brandwith is too small.======== Daemon connection timeout and down state limit =========
    # timeout: how many seconds to consider a node don't answer
    data_timeout                   1203

    # maxdata_check_attemptstimeout: how many fail checksecond to consider a configuration thistransfert daemonto asbe DEADfailed
    max_check_attempts# because the network brandwith is too small.
    data_timeout    3

    # Check this daemon every X seconds120

    # max_check_intervalattempts: how many fail check to consider this daemon    60


as DEAD
    #=max_check_attempts        3

    # Check this daemon every X seconds
    check_interval            60



    #======== Modules to enable for this daemon =========
    # Available:
    # - Simple-log            : save all logs into a common file
    # - WebUI                 : visualisation interface
    # - Graphite-Perfdata     : save all metrics into a graphite database
    # - sla                   : save sla into a database
    # - Livestatus            : TCP API to query element state, used by nagios external tools like NagVis or Thruk
    modules # - event-manager-writer  : save events for events manager (do not forget to activate the module in your webui to see data)
    modules                   Simple-log, WebUI, Graphite-Perfdata, sla


, event-manager-writer
    

    #======== Realm and architecture settings =========
    # Realm to set this daemon into
    realm                    All

    # 1 = take data from the daemon realm and its sub realms
    # 0 = take data only from the daemon realm
    manage_sub_realms        1

    # Is enabled, then this broker will receive data (logs and) from the arbiter
    manage_arbiters          1

    # In NATted environments, you declare each satellite ip[:port] as seen by
    # *this* broker (if port not set, the port declared by satellite itself
    # is used)
    #satellitemap    scheduler-1=1.2.3.4:7768, poller-1=1.2.3.5:7771


    #======== Memory protection =========
    # Are the daemon module process and worker process are waiting for enough
    # memory to be available before being launch. Default: 1 (enabled)
    broker__manage_brok__enable_sub_processes_memory_usage_protection   1

    # The sub process memory usage protection can have a system reserved memory
    # that won't be used by theses sub process when launched
    # By default: 0 (no reserved memory)
    # Example: 10  (means 10% of the total memory is reserved for the system)
    broker__manage_brok__sub_process_memory_usage_system_reserved_memory    0

    # If a sub process cannot be started because of the protection, how many seconds
    # it will be retry and wait that the system memory is freed until it fail to start
    # By default: 5 (seconds)
    broker__manage_brok__sub_processes_memory_usage_protection_max_retry_time   5


    #======== Brok pusher worker ==========
    # The broker spawn broks pusher sub process to push to external modules (like WebUI)
    # the broker will look at this worker execution time, and will kill if it timeout
    # The broker spawn broks pusher sub process to push to external modules (like WebUI)
    # the broker will look at this worker execution time, and will kill if it timeout
    # The broker will compute the average execution time of previous workers to
    # decide about how many time this worker will take based on:
    # number of broks to send / past average send speed (broks/s)
    # If Thethis brokertime willis computereach, theit averagemeans executionthat timethe ofpusher previousprocess workersis tokilled

    # decide about how many time this worker will take based on: For small amount of broks to send, it should lead to ridicusly small allowed execution time
    # numberand ofthe broksfac to sendspawn /the pastsub averageprocess sendcan speed (broks/s)
    # If this time is reach, it means that the pusher process is killed
be higher than this value, so we are using a minimal
    # execution timeout
    # For small amount of broks to send, it should lead to ridicusly small allowed execution time Default: 5 (second)
    broker__manage_brok__sub_process_broks_pusher_min_execution_timeout           5

    # and In order to manage the facfact to spawnthat the sub processserver can beslow higherdown thanduring this valuesend, soyou wecan are usingsetup a minimal
    # execution timeout ratio that will be used to increase the allowed timeout by multiply it
    # Default: 5 (second)
    broker__manage_brok__sub_process_broks_pusher_min_execution_timeout           5

security_ratio      # In order to manage the fact that the server can slow down5

 during this send, you# canAt setupthe a
broker start without stats, #this ratio thatvalud will be used to increasefor the allowed timeout by multiply it
    # Default: 240 5(seconds)
    broker__manage_brok__sub_process_broks_pusher_pushermax_security_ratioexecution_timeout           240

    # If a sub process reach 5

a timeout, it will #be Atkilled theand brokerrelaunched. startAfter withoutmax statsretry,
   this valud# willthe beattached usedmodule forwill thebe timeoutrestarted
    # Default: 240 (seconds)3
    broker__manage_brok__sub_process_broks_pusher_max_execution_timeout      retry     240

    # If a sub process reach a timeout, it will be killed and relaunched. After max retry, 3


    # the attached module will be restarted======== VMWare / ESXi ==========
    # Default: 3
    broker__manage_brok__sub_process_broks_pusher_max_retry               1 (default) = if vmware get the ESXi CPU stats value, 0 = do not get value
    vmware__statistics_compute_enable        31


    #======== Enable or not this daemon =========
    # 1 = is enabled, o0 = is disabled
    enabled                  1

}