Versions Compared

Old Version 7

changes.mady.by.user Serge Dewailly

Saved on

compared with

New Version 8

changes.mady.by.user Serge Dewailly

Saved on

Key

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

Goal of this source

Connecting Shinken Enterprise to Active Directory will allow you to automatically detect your windows servers.

  

Configure this source

You can enable it by editing the configuration file /etc/shinken/modules/activ-dir-import.cfg

All you need is to set the following parameters:

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 not 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:


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 :


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 :

 

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