Project: Netdata (Observability and Analysis / Observability)
File: openldap.md

<!--startmeta customediturl: "https://github.com/netdata/netdata/edit/master/src/collectors/python.d.plugin/openldap/README.md" meta_yaml: "https://github.com/netdata/netdata/edit/master/src/collectors/python.d.plugin/openldap/metadata.yaml" sidebar_label: "OpenLDAP" learn_status: "Published" learnrelpath: "Collecting Metrics/Authentication and Authorization" most_popular: False message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" endmeta--> <img src="https://netdata.cloud/img/statsd.png" width="150"/> Plugin: python.d.plugin Module: openldap <img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" /> This collector monitors OpenLDAP metrics about connections, operations, referrals and more. Statistics are taken from the monitoring interface of a openLDAP (slapd) server This collector is supported on all platforms. This collector only supports collecting metrics from a single instance of this integration. This collector doesn't work until all the prerequisites are checked. The default configuration for this integration does not impose any limits on data collection. The default configuration for this integration is not expected to impose a significant performance impact on the system. Metrics grouped by scope. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. These metrics refer to the entire monitored application. This scope has no labels. Metrics: | Metric | Dimensions | Unit | |:|:-|:-| | openldap.total_connections | connections | connections/s | | openldap.traffic_stats | sent | KiB/s | | openldap.operations_status | completed, initiated | ops/s | | openldap.referrals | sent | referrals/s | | openldap.entries | sent | entries/s | | openldap.ldap_operations | bind, search, unbind, add, delete, modify, compare | ops/s | | openldap.waiters | write, read | waiters/s | There are no alerts configured by default for this integration. Follow instructions from https://www.openldap.org/doc/admin24/monitoringslapd.html to activate monitoring interface. Install python ldap module From pip package manager ```bash pip install ldap ``` With apt package manager (in most deb based distros) ```bash apt-get install python-ldap ``` With yum package manager (in most rpm based distros) ```bash yum install python-ldap ``` Use the `ldappasswd` utility to set a password for the username you will use. The configuration file name for this integration is `python.d/openldap.conf`. You can edit the configuration file using the `edit-config` script from the Netdata . ```bash cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata sudo ./edit-config python.d/openldap.conf ``` There are 2 sections: Global variables One or more JOBS that can define multiple different instances to monitor. The following options can be defined globally: priority, penalty, autodetectionretry, updateevery, but can also be defined per JOB to override the global

Additionally, the following collapsed table contains all the options that can be configured inside a JOB definition. Every configuration JOB starts with a `job_name` value which will appear in the dashboard, unless a `name` parameter is specified. <details><summary>Config options</summary> | Name | Description | Default | Required | |:-|:--|:-|:--:| | update_every | Sets the default data collection frequency. | 5 | no | | priority | Controls the order of charts at the netdata dashboard. | 60000 | no | | autodetection_retry | Sets the job re-check interval in seconds. | 0 | no | | penalty | Indicates whether to apply penalty to update_every in case of failures. | yes | no | | name | Job name. This value will overwrite the `job_name` value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works. | | no | | username | The bind user with right to access monitor statistics | | yes | | password | The password for the binded user | | yes | | server | The listening address of the LDAP server. In case of TLS, use the hostname which the certificate is published for. | | yes | | port | The listening port of the LDAP server. Change to 636 port in case of TLS connection. | 389 | yes | | use_tls | Make True if a TLS connection is used over ldaps:// | no | no | | usestarttls | Make True if a TLS connection is used over ldap:// | no | no | | cert_check | False if you want to ignore certificate check | True | yes | | timeout | Seconds to timeout if no connection exist | | yes | </details> A basic example configuration. ```yaml username: "cn=admin" password: "pass" server: "localhost" port: "389" check_cert: True timeout: 1 ``` To troubleshoot issues with the `openldap` collector, run the `python.d.plugin` with the debug option enabled. The output should give you clues as to why the collector isn't working. Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`. ```bash cd /usr/libexec/netdata/plugins.d/ ``` Switch to the `netdata` user. ```bash sudo -u netdata -s ``` Run the `python.d.plugin` to debug the collector: ```bash ./python.d.plugin openldap debug trace ```