Dynatrace offers this Synthetic LDAP extension to validate and check your LDAP health.
Matching filters will be flagged as successful synthetic tests as well as measuring response time performance.
Get started
Requirements
ActiveGate must be 1.265+ (Windows or Linux ActiveGates)
Dynatrace version 1.265+
Communication ports between ActiveGate and LDAP server must be open on whichever port runs on.
If using a Linux ActiveGate and you would like to use the ldapsearch feature (optional), ldapsearch must be installed on your Linux ActiveGate. This is not supported on Windows.
Configuration
LDAP Server: Hostname or IP of your LDAP server.
LDAP Port: 389 is the default for LDAP. If using SSL, make sure you also change this port number to reflect the correct SSL port.
Test name: The name for this Synthetic test
Test location: Enter a name of the location where this test will be running from. Otherwise the default name is "ActiveGate".
Use credential vault: Use this feature if you would like to use a pre-stored Username/Password from your Dynatrace credential vault.
LDAP Bind DN: This would be the username to log into your LDAP server.
LDAP Password: Password for the username above.
LDAP Base DN: Entry DN from where to start the search.
Use ldapsearch: This is in case you would like to use a ldapsearch command expression instead. This is due to some LDAP tools having different format and custom properties and fields that the normal LDAP searches cannot see. A ldapsearch might return or provide more hidden fields. You will rarely need to use this feature and it requires you have ldapsearch installed on your ActiveGates.
LDAP filters: Add any filters to get a better focus your search and speed it up.
LDAP attributes: Which attributes to return.
LDAP matcher: The exact text to match in the result. If a matcher is entered, your test will be flagged as successful if the text is found, otherwise, marked as failed if not found.
LDAP timeout: Number of seconds for the request to wait before timing out if no response.
Dynatrace token: Because data is pushed as a third party synthetic test using the API, you must enter an API token with "Create and read synthetic monitors, locations and nodes" scope.
Polling frequency: Interval this synthetic test will run. By default, it will run every 1 minute.