Page History

...

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 XXXXXXXXXXXXXXXX
	_SE_UUID_HASH XXXXXXXXXXXXXXXX
	# End of Shinken Enterprise part

	module_name cfg-file-shinken
	module_type cfg-file-import
	cfg_path /etc/shinken/local-import.cfg
}

Having more than 1 cfg-file-

...

shinken source defined.

When you have many source of configuration (for example 2 nagios to a new configuration in addition to the one deliver in shinken  to import in your shinken), we advise you to create 2 automatic sources.

If you keep only one source, you will have to merge the 2 nagios Shinken configurations in the same directory. You may have naming conflict...

To have an additional source:

1.  Copy the /etc/shinken/local-import.cfg  and rename it into you source_name_import.cfg
    
2. Copy  /etc/shinken/modules/cfg-file-nagiosshinken.cfg  into an other cfg file name and configure it.
   • Remember that the module_name must be unique (Example: my_module_name)

   • cfg_path must be set to source_name_import.cfg

     
     
3. Copy  /etc/shinken/sources/cfg-file-nagiosshinken.cfg into an other cfg file name and configure it.
   
   • Remember that the source_name must be unique.
     (Example:  my_source_name)
      
   • modules must be set to the new module you just define (my_module_name)
      
4. Then you must declare the source_name source in the file /etc/shinken/synchronizers/synchronizer-master.cfg.
   
   • add the source name in the line sources

   • sources syncui,cfg-file-shinken,active-dir,sync-vmware,cfg-file-nagios,discovery, my_source_name

...