Page History

#===============================================================================
# RECEIVERSCHEDULER
#===============================================================================
# The scheduler receiveris managesa passive"Host informationmanager". It's gets justthe ahosts "buffer"and whichtheir willservices,
# loadschedules passivethe moduleschecks and betransmit readthem byto the arbiter to dispatch data. pollers.
# Description: The scheduler is responsible for:
# - Scheduling checks
# - Computing states
# - Enqueing jobs
#===============================================================================

define receiver {

scheduler {

# 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-scheduler-1e36315a5ade11e59189080027f08538
    _SE_UUID_HASH       ff9b3be8ddb1cee8f8fae6f02aa2defe
# End of Shinken Enterprise part


    #======== Daemon name and address =========
    # Daemon name. Must be unique
    receiverscheduler_name             receiverscheduler-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                      77737768

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



    #======== RealmMaster andor architecturespare settingsselection =========
    # Realm1 to= setis this daemon into
    spare                     0

    # Realm to set this daemon intoa spare, 0 = is not a spare
    realmspare                     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 =========
    # Exactly one retention module can be chosen. No modules or more than one retention will result in a configuration error displayed in the output of the shinken-healthcheck command.
    # Available:
    # - ws-arbiter: webservice interface PickleRetentionFile : (if you have only one scheduler into a realm) save retention data (element state and scheduling) into a file
    # - MongodbRetention    : (if you have more than one scheduler into a realm) save retention data (element state and scheduling) into a mongodb database
    modules                  PickleRetentionFile



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

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


    #======== 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

}