Hi,
according to your documentation of the OpenLDAP integration custom queries are supposed to support the search_scope setting:
https://github.com/DataDog/integrations-core/blob/master/openldap/datadog_checks/openldap/data/conf.yaml.example#L61
However looking at the code it seems like this value is never used in the actual check code that executes the custom queries against the LDAP endpoint:
https://github.com/DataDog/integrations-core/blob/master/openldap/datadog_checks/openldap/openldap.py#L144
Since the example config shows (objectClass=*) as the search_filter it would definitely make sense to use this option in order to be able to restrict the amount of results of simple availability checks based on requirements.
Thanks!
Hi,
according to your documentation of the OpenLDAP integration custom queries are supposed to support the
search_scopesetting:https://github.com/DataDog/integrations-core/blob/master/openldap/datadog_checks/openldap/data/conf.yaml.example#L61
However looking at the code it seems like this value is never used in the actual check code that executes the custom queries against the LDAP endpoint:
https://github.com/DataDog/integrations-core/blob/master/openldap/datadog_checks/openldap/openldap.py#L144
Since the example config shows
(objectClass=*)as thesearch_filterit would definitely make sense to use this option in order to be able to restrict the amount of results of simple availability checks based on requirements.Thanks!