Page History

L'Arbiter est capable de rendre inactifs les démons distants désactivés (lorsque la propriété "enabled" est mise 0 dans leurs fichiers cfg)

Exemple: Depuis le serveur central, je décide de désactiver un Poller distant en passant la propriété "enabled" à 0 dans son fichier de définition. Je redémarre l'Arbiter. Le Poller distant sera affiché comme "désactivé" depuis son shinken-healthcheck local.

Il n'est donc pas nécessaire d'éteindre un démon qui n'est plus utilisé sur une machine distante.

#===============================================================================
# ARBITER
#===============================================================================
# Description: The Arbiter is responsible for:
# - Loading, manipulating and dispatching the configuration
# - Validating the health of all other Shinken daemons

#===============================================================================
# IMPORTANT: If you use a spare arbiter you MUST set the host_name on each
# servers to its real DNS name ('hostname' command).
#===============================================================================

define arbiter {

    #======== Daemon name and address =========
    # Daemon name. Must be unique
    arbiter_name      arbiter-master

    # Hostname used by the Arbiter daemon to distinguish master and slave Arbiters (when having multiple Arbiters).
    # If not defined, the Arbiter daemon will use its server name, but it can be used with only one Arbiter in the
    # Shinken architecture.
    #host_name        HOSTNAME

    # IP/fqdn of this daemon
    address           localhost   ; DNS name or IP

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

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


    #======== Daemon connection timeout and down state limit =========
    # Parameters used by Arbiter-master and Arbiter-spare to put respectively the other demon as not available.
 
    #---------------
    # timeout: value specific to each arbiter. When trying to PING this Arbiter, any daemon / healtcheck / shinken checks will consider theit PINKas asunreachable KOafter this timeout
    # All cases:
    #   - Arbiter master wait the arbiter spare for this timeout duration
    #   - shinken-healtcheck/shinken check will use it to wait for the arbiter master or spare
    #   ( default 3 )
    # NOTE: this parameter is NOT used by the arbiter spare to wait for master's death before
    #       take over the configuration. For this, look at max_check_attempts & check_interval
    timeout              3
 
    #---------------
    # data_timeout: how many second to consider a configuration transfert to be failed to the arbiter spare
    #   - to be defined on the Arbiter-spare
	    #   - Used by the Arbiter-master
    #	   ( default 120 )
    data_timeout         120
 
    #---------------
    # max_check_attempts: how many fail check to consider this daemon as DEAD
    #   Defined on the Arbiter-spare 
	#     -> Used by the Arbiter-master to declare the spare as DEAD ( so after a wait of X max_check_attempts * check_interval seconds )
    #
    #   or 
    #
    #   Defined on the Arbiter-master
	#     -> Used by the Arbiter-spare to take over the role of arbiter-master ( so after a wait of X max_check_attempts * check_interval seconds )
    #
    max_check_attempts   3

    #---------------
    # check_interval: check every X seconds or use to know how many seconds to wait for the arbiter master
    #   Defined on the Arbiter-spare 
	#     -> Used by the Arbiter-master to declare the spare as DEAD ( so after a wait of X max_check_attempts * check_interval seconds )
    #
    #   or 
    #
    #   Defined on the Arbiter-master
	#     -> Used by the Arbiter-spare to take over the role of arbiter-master ( so after a wait of X max_check_attempts * check_interval seconds )
    #
    check_interval       60


    #======== Master or spare selection =========
    # 1 = is a spare, 0 = is not a spare
    spare             0


    #======== Modules to enable for this daemon =========
    # Available:
    # - synchronizer-import : [mandatory] will allow to get configuration from the synchronizer
    # - architecture-export : will open a socket that listens for Shinken architecture descriptions to generate corresponding hosts and NagVis maps
    modules    	      synchronizer-import



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

    #======== Enable or not this daemon =========
    # 1 = is enabled, 0 = is disabled
    # enabled:  if the version between the arbiter and daemons mismatch, daemons refuse the arbiter configuration and an error is reported
    # disabled: if the version between the arbiter and daemons mismatch, daemons accept the arbiter configuration and a warning is reported.
    mismatch_version_error 1
}