Versions Compared

Old Version 20

changes.mady.by.user Jroy

Saved on

compared with

New Version 21

changes.mady.by.user Jroy

Saved on

Key

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

Overview

The Active directory Source will connect to Active Directory:

  • it will detect automatically new windows servers and collect data on them.
  • it will list user defined in the AD.

Server, Data and User can be retrieved in sub-part of the AD, preventing to load all the AD, or filter to collect only appropriate data.

Panel
titleOn this page

Table of Contents

Configuration

To define a Active Directory source:

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

Table of Contents

Info
titleNote

During the Shinken Enterprise installation process, an Active Directory source called active-diris defined but set to inactive.
It is mainly to provide Administrator with an example.

sources/activ-dir-import.cfg

 Property Example Description
source_name active-dir Name of this source. Must be unique.
order 2 Order in the merge algorithm of this source data. Look in the Synchronizer page for more information about it.
import_interval 5 Launch this source every import_inverval minutes.
modulesactive-dir 
enabled0 
descriptionThis source is about loading hosts from active directories 
 

module/activ-dir-import.cfg

Update these parameters in the cfg file:

PropertyDefaultDescription
urlldap://YOURDCFQDN/URL of your Active Directory server.
base dc=YOUR,dc=DOMAIN,dc=comBase OU for your objects discovery.
hosts_baseOU=DataCenter Servers,dc=YOUR,dc=DOMAIN,dc=comBase OU for the hosts discovery.
contacts_basedc=YOUR,dc=DOMAIN,dc=comBase OU for the contacts discovery.
usernameSHINKEN@YOURDOMAIN.comUsername used to connect to the Ldap server.
passwordPASSWORDPassword used by the user to connect to the Ldap server.

This connection information will allow the source to connect to your Active Directory. It only needs a « read only » account.

Info
titleNote

Shinken Enterprise’s main purpose is monitoring servers, therefore we suggest you DON'T load all your Active Directory elements like computers. 

  

Filtering and tagging

This source also includes other parameters that will allow you to automatically “tag” your servers based on your active directory information:

  • hosts_tag: each loaded hosts will have at least this tag
  • contacts_tag: each loaded contacts will have at least this tag

Contacts to load can be easily filtered with the contacts_filters parameter.

Tagging hosts based on their OU (Organization Unit) is possible. This is done with the hosts_tag_* parameters.

For example, if you want to add the exchange tag to all the servers which are below

the OU=Email Collaboration Servers,OU=DataCenter Servers,DC=YOUR,dc=DOMAIN,dc=com OU,

you can set this parameter:

 

Code Block
hosts_tag_exchange  OU=Email Collaboration Servers,OU=DataCenter Servers,DC=YOUR,dc=DOMAIN,dc=com


 

 

Setting up ldap object matching with the hosts_match_* parameters is also possible.

 

For example, if you want to add the enterprise tag to all the ldap object that match the string Enterprise in their operatingSystem property,

you only need to setup :

 

Code Block
hosts_match_operatingSystem_enterprise        Enterprise


 

 This also works with groups.

 For example, if you want to add the domain-admins tag to the users that are in the CN=Domain Admins,CN=Users,DC=YOUR,dc=DOMAIN,dc=com OU,

setup :

 

Code Block
 contacts_match_memberOf_domain-admins         CN=Domain Admins,CN=Users,DC=YOUR,dc=DOMAIN,dc=com


 

  

Custom fields and host templates setting

If presents into the Ldap objects, some fields are automatically set on your host objects:

Host dataLdap field
_OSoperatingSystem
_OS_SPoperatingSystemServicePack
_IPif the server can resolve the PTR dNSHostName entry
_FQDNif the server can resolve the dNSHostName entry