ZenPack:LDAP Monitor (Core)

From Zenoss Wiki
This is the approved revision of this page, as well as being the most recent.
Jump to: navigation, search

Note: This is a Core ZenPack which can be found in the Core Zenoss RPM, and is fully documented in the Zenoss Extended Monitoring Guide. If you did not install this pack when you installed Zenoss Core, it can be found in $ZENHOME/packs.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.LDAPMonitor
Link to more docs
View Documentation




LDAP Monitor (Core) ZenPack

LDAPMonitor monitors the response time of an LDAP server (in milliseconds).

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is part of Zenoss Core. Open Source users receive community support for this ZenPack via our online forums. Enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Background

The ZenPacks.zenoss.LDAPMonitor ZenPack monitors the response time of Lightweight Directory Access Protocol (LDAP) servers.


The response time unit of measurement is milliseconds.


Prerequisites

Prerequisite Restriction
Product Zenoss platform 4.x, Zenoss 2.2 or higher
Required ZenPacks ZenPacks.zenoss.LDAPMonitor


Enable monitoring for a device

Note: The LDAPServer template must be bound to the device class or device you want to monitor.


  1. Select Infrastructure from the navigation bar.
  2. Click the device name in the device list. The device overview page appears.
  3. Select Configuration Properties from the left panel.
  4. Modify configuration property values as needed for your environment. Check with your LDAP administrator for more information.
    LDAPServer Configuration Properties
    Property Description
    zLDAPBaseDN The Base Distinguished Name for your LDAP server. Typically this is the organization's domain name (for example, dc=foobar,dc=com)
    zLDAPBindDN The Distinguished Name to use for binding to the LDAP server, if authentication is required
    zLDAPBindPassword The password to use for binding to the LDAP server, if authentication is required


  5. Click Save.
  6. Expand Monitoring Templates, and then select Device from the left panel.
  7. Select Bind Templates from the Action menu. The Bind Templates dialog appears.
  8. Add the LDAPServer template to the list of selected templates, and then click Submit. The LDAPServer template is added to the list of monitoring templates.
  9. Select the LDAPServer template and change options as needed.
    LDAPServer Basic Data Source Options
    Option Description
    Port The port to connect to LDAP server (default 389)
    Base Distinguished Name Defaults to ${here/zLDAPBaseDN}
    Bind Password Defaults to ${here/zLDAPBindPassword}
    Use SSL Use SSL for the connection


    Note: If your LDAP servers require SSL or a custom port, select the ldap data source, and then change the Use SSL and Port fields as needed.

  10. Validate your configuration by running zencommand. Verify that the check_ldap or check_ldaps command correctly connects to your LDAP server:
    zencommand run -v10 -d yourdevicenamehere


Daemons

Type Name
Performance Collector zencommand

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.LDAPMonitor-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone git://github.com/path/to/repo
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.zenoss.LDAPMonitor
  4. Finally, restart these serivices:
    $ zenoss restart

Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus