Versions Compared

Old Version 8

changes.mady.by.user Jroy

Saved on

compared with

New Version Current

changes.mady.by.user Jroy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

 Migrating from Nagios to Shinken Enterprise is very easy. You can import your previous Nagios configuration using the cfg-file-nagios source.

Configuration

To define a nagios cfg source:

  1. Configure the module in the file /etc/shinken/modules/cfg-file-nagios.cfg
    to define the behaviour of the module
  2. Then configure the source in the file /etc/shinken/sources/cfg-file-nagios.cfg
    to enable the source and call the module configured in step 1.
  3. Then you must declare the VMware cfg-file-nagios source in the file /etc/shinken/synchronizers/synchronizer-master.cfg.


Info
titleNote

During the Shinken Enterprise installation process, a VMware cfg-file-nagios module called synccfg-file-vmwarenagios is defined but set to inactive.
It is mainly to provide Administrator with an example.

sources/

...

cfg-file-

...

nagios.cfg

PropertyExampleDescription

source_name

synccfg-file-vmwarenagiosName of this source. Must be unique.
order3Order in the merge algorithm of this source data. Look in the Synchronizer page for more information about it.
import_interval5Launch this source every import_inverval minutes. If you set it to 0, the module will never be launcher automatically
modulessynccfg-file-vmwarenagiosThe module to launch
enabled0

1 - Activate the source

0 - Viewed in the interface, but doesn't collect data nor import objects.

description        

This source is about loading

hosts from VMware vSphere

a
Nagios/Centreon compatible
configuration

A description to show on the UI.

...

modules/

...

cfg-file-

...

nagios.cfg

Here is the list of parameters required by the module to be updated the in cfg file.

PropertyDefault (if not set)Description
vcenter vcenter.fqdn.comFQDN (Fully Qualified Domain Name) or IP Address of the vSphere server.
user                           

DOMAIN\user

User used to connect to the vSphere server. Must be a read-only account.
password                  

PASSWORD

Password for the user access.
esx_templates esxHost template to set on the detected esx or esxi hosts.
module_namecfg-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.

Code Block
...
cfg_file=dependencies.cfg
...
cfg_dir=hosts
cfg_dir=services
..
vm_templates vmware-vmHost template to set on the detected virtual servers
.
Info
titleNote

The default column shows the value used by the module if the Shinken Enterprise Administrator didn't set update it.

Here there an example of the module definition:

Code Block
define module{
	# Shinken module_nameEnterprise. Lines added by import core. sync-vmware
	# Do module_typenot remove it, it's used by sync-vmware
Shinken Enterprise check_esx_pathto update  /var/lib/shinken/libexec/synchronizer/esx_discovery.pl
  vcenter          myesx.ovh.com
  user             admin
  password         XYZ
  esx_templates    esx
  vm_templates     vmware-vm
}

 

Automatic templates for Virtual S

 

Migrating from Nagios to Shinken Enterprise is very easy

...

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 defined.


When you have many source of configuration (for 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 configurations in the same directory. You may have naming conflict...


To have an additional source:

  1. Copy  /etc/shinken/modules/cfg-file-nagios.cfg  into an other cfg

...

All you need to do is to set the following parameters:

  • cfg_path                   /etc/nagios/nagios.cfg

Note: you must copy all your Nagios configuration into the Shinken Enterprise.

...

  1. file name and configure it.
    • Remember that the module_name must be unique (Example: my_module_name)

    Copy  /etc/shinken/sources/cfg-file-nagios.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)
       
  2. 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

 

Code Block
define synchronizer {
	...
	sources syncui,cfg-file-shinken,active-dir,sync-vmware,cfg-file-nagios,discovery,my_source_name
	...
}