Page History

#===============================================================================
# RECEIVER
#===============================================================================
# The receiver manages passive information. It's just a "buffer" which will
# load passive modules and be read by the arbiter to dispatch data.
#===============================================================================

define receiver {
# 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-receiver-1565c87e5ade11e59d26080027f08538
    _SE_UUID_HASH       b0030c9912c63862c3957736875cae84
# End of Shinken Enterprise part

    #======== Daemon name and address =========
    # Daemon name. Must be unique
    receiver_name             receiver-master

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

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

    # 0 = use HTTP, 1 = use HTTPS
    use_ssl	                       0



    #======== Realm and architecture settings =========
    # Realm to set this daemon into
    spare                     0

    # Realm to set this daemon into
    realm                     All

    # 1 = will directly send commands to the schedulers if it know about the hostname in the command
    direct_routing            0



    #======== Daemon connection timeout and down state limit =========
    # timeout: how many seconds to consider a node don't answer
    timeout                   3

    # data_timeout: how many second to consider a configuration transfert to be failed
    # because the network brandwith is too small.
    data_timeout              120

    # max_check_attempts: how many fail check to consider this daemon as DEAD
    max_check_attempts        3

    # Check this daemon every X seconds
    check_interval            60



    #======== Modules to enable for this daemon =========
    # Available:
    # - wsreceiver-module-arbiterwebservice: webservice interface
    modules


    #======== Host & checks sharding ========
    # Some receiver modules can register to some host/checks data
    # and so if configured for it, receiver will have all the host/checks
    # useful DATA for the templates
    # By default this is disabled
    #elements_sharding_enabled                0

    # Will only send host (and theirs checks) of this template
    #elements_sharding_filter_by_template     filter-template

    # Will only take DATA declared local to theses templates
    #elements_sharding_add_data_of_templates  template-with-data1,template-wit-data2

    # Host are shards across receivers. Set a higher weight if this receiver
    # need to manage more hosts than the others
    #elements_sharding_weight                 1


    #======== VMWare / ESXi ==========
    # 1 (default) = if vmware get the ESXi CPU stats value, 0 = do not get value
    vmware__statistics_compute_enable     1


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