define scheduler {
    [...]
    modules                   MongodbRetention
    [...]
}

service shinken-arbiter restart

#===============================================================================
# MongodbRetention
#===============================================================================
# Daemons that can load this module:
# - scheduler
# This module save scheduler retention data (element state and scheduling) into a mongodb server
#===============================================================================


define module {

# 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-module-d98ab73a5adb11e5a2df080027f08538
    _SE_UUID_HASH        c8c8f39897b928ee624da45934b38fd9
# End of Shinken Enterprise part

    #======== Module identity =========
    # Module name. Must be unique
    module_name     MongodbRetention

    # Module type (to load module code). Do not edit.
    module_type     mongodb_retention


    #======== Mongodb connection =========

    # uri: to connect the mongodb server
    uri                     mongodb://localhost/?safe=false

    #======== IMPORTANT =============
    # Note that if the parameter "use_ssh_tunnel" is set to 1,
    #  the mongodb connection will be launched through a SSH tunnel
    #  opened from the scheduler server to the mongodb server.
    # It will automatically parse the URI parameter to get the distant server
    #  and will create a SSH tunnel by using either the user defined by the "ssh_user" property
    #  or the shinken user.
    # The SSH key used for this is the one that is automatically generated
    #  at the installation or the key defined by the parameter "ssh_keyfile".
    # You can deploy it by launching on the scheduler server:
    #   ssh-copy-id -i ~shinken/.ssh/id_rsa.pub shinken@MONGODB-SERVER

    # If you want to secure your mongodb connection you can enable the ssh use_ssh_tunnel that will
    # allow all mongodb to be encrypted & authenticated with SSH
    # Should use a SSH tunnel (Default 0=False)
    # use_ssh_tunnel          0

    # If the SSH connection goes wrong, then retry use_ssh_retry_failure time
    # Default: 1
    # use_ssh_retry_failure   1

    # SSH user/keyfile in order to connect to the mongodb server.
    # Default: shinken
    # ssh_user                shinken

    # Default: ~shinken/.ssh/id_rsa
    # ssh_keyfile             ~shinken/.ssh/id_rsa

    # Timeout used to test if the SSH tunnel is viable or not
    # Default: 2
    # ssh_tunnel_timeout        2

    # Timeout for reading 5000 item in second
    # Default value : 10s
    # mongo_timeout  10

    # Number of retry if mongo is not accessible
    # Default value : 3
    # mongo_max_connections_retry    3
    # Delay before next retry
    # Default value : 1s
    # mongo_wait_before_retry 1


    # database: which mongodb database to use
    database        shinken
    
    # Advanced option if you are running a cluster mongodb environment
    # replica_set

    # Retention SAVE:
    # the retention save will spawn process workers (max to 4) and
    # such process can fail (timeout)

    # Worker timeout: Global time for your workers to work. If a worker still
    # runs after worker_timeout seconds (and so numerous try)), then it will be killed and the error will
    # be raised into your monitoring
    # Default: 120
    # worker_timeout   120

    # Worker try timeout: Time for a one try data save. If one worker process still runs after
    # worker_one_try_timeout seconds, it will be killed and a new worker process will be spawn
    # to replace it
    # note: it must be lower than the worker_timeout
    # Default: 30
    # worker_one_try_timeout   30

    # Max number of workers: if you want to limit the number of workers launched, you can change this parameter
    # By default the number of workers will be the number of CPUs but no more than max_number_of_workers (by default 4)
    # max_number_of_workers   4


    #======== Memory protection =========
    # Are the module worker process are waiting for enough
    # memory to be available before being launch. Default: 1 (enabled)
    scheduler__retention_mongo__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)
    scheduler__retention_mongo__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)
    scheduler__retention_mongo__sub_processes_memory_usage_protection_max_retry_time   5

    #======== INTERNAL options =========
    #INTERNAL : DO NOT EDIT FOLLOWING PARAMETER WITHOUT YOUR DEDICATED SUPPORT
    # == Number of day we conserve retention data, after this time, we will delete data. By default it is 7 days ==
    #nb_of_max_retention_day	    7
    # == maximum number of elements load in one bulk pass ==
    #size_chunk_to_load	        1000
    # == maximum number of elements delete in one bulk pass ==
    #size_chunk_to_delete	        1000
}                                                                                            

Il est conseillé de n'avoir plusieurs modules de rétention que dans le cas d'une migration. (Ex: passage d'une base de données base1 à une base2, on aura un module MongodbRetention avec la base1, un autre avec la base2, on désactivera alors le premier module pour le prochain redémarrage))

    #======== Mongodb connection =========
    # uri: to connect the mongodb server
    uri                     mongodb://localhost/?safe=false

    # Timeout for reading 5000 item in second
    # Default value : 10s
    # mongo_timeout  10

    # Number of retry if mongo is not accessible
    # Default value : 3
    # mongo_max_connections_retry    3
    # Delay before next retry
    # Default value : 1s
    # mongo_wait_before_retry 1


    # database: which mongodb database to use
    database        shinken
    
    # Advanced option if you are running a cluster mongodb environment
    # replica_set

# If you want to secure your mongodb connection you can enable the ssh use_ssh_tunnel that will
# allow all mongodb to be encrypted & authenticated with SSH
# Should use a SSH tunnel (Default 0=False)
# use_ssh_tunnel 0

# If the SSH connection goes wrong, then retry use_ssh_retry_failure time
# Default: 1
# use_ssh_retry_failure 1

# SSH user/keyfile in order to connect to the mongodb server.
# Default: shinken
# ssh_user shinken

# Default: ~shinken/.ssh/id_rsa
# ssh_keyfile ~shinken/.ssh/id_rsa

# Timeout used to test if the SSH tunnel is viable or not
# Default: 2
# ssh_tunnel_timeout 2

    # Retention SAVE:
    # the retention save will spawn process workers (max to 4) and
    # such process can fail (timeout)

    # Worker timeout: Global time for your workers to work. If a worker still
    # runs after worker_timeout seconds (and so numerous try)), then it will be killed and the error will
    # be raised into your monitoring
    # Default: 120
    # worker_timeout   120

    # Worker try timeout: Time for a one try data save. If one worker process still runs after
    # worker_one_try_timeout seconds, it will be killed and a new worker process will be spawn
    # to replace it
    # note: it must be lower than the worker_timeout
    # Default: 30
    # worker_one_try_timeout   30

    # Max number of workers: if you want to limit the number of workers launched, you can change this parameter
    # By default the number of workers will be the number of CPUs but no more than max_number_of_workers (by default 4)
    # max_number_of_workers   4

    #======== Memory protection =========
    # Are the module worker process are waiting for enough
    # memory to be available before being launch. Default: 1 (enabled)
    scheduler__retention_mongo__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)
    scheduler__retention_mongo__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)
    scheduler__retention_mongo__sub_processes_memory_usage_protection_max_retry_time   5

#======== INTERNAL options =========
#INTERNAL : DO NOT EDIT FOLLOWING PARAMETER WITHOUT YOUR DEDICATED SUPPORT
# == Number of day we conserve retention data, after this time, we will delete data. By default it is 7 days ==
#nb_of_max_retention_day 7
# == maximum number of elements load in one bulk pass ==
#size_chunk_to_load 1000
# == maximum number of elements delete in one bulk pass ==
#size_chunk_to_delete 1000

Cette partie ne doit pas être modifiée sans votre support