...
| Property | Default (if not set) | Description | ||
|---|---|---|---|---|
| module_name | cfg-file-nagios | Name of this module. Must be unique. | ||
| cfg_path | /etc/nagios/nagios.cfg | the path of the cfg file that list file and directories to import.
|
| Info | ||
|---|---|---|
| ||
The default column shows the value used by the module if the Shinken Enterprise Administrator didn't update it. |
Here there an example of the module definition:
| Code Block |
|---|
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-nagios
module_type cfg-file-import
cfg_path /etc/nagios/nagios.cfg
} |
Having more than 1 cfg-file-nagios
...
source in the administration.
When you have many source of source of configuration (for exemple example 2 nagios 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 configuration in the same directory. You may have naming conflict...
To have an additional source,:
- Copy /etc/shinken/modules/cfg-file-nagios.cfg into an other cfg file name and configure it it.
- Remember that the module_name must be unique (Example: my_module_name)
- 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)
- Remember that the module_name must be unique (Example: my_module_name)
- 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
...