LDAP Synthetic extension

Georgi_Vuldzhev — Wed, 29 Apr 2026 06:17:43 GMT

Hi everyone,

I am working for the first time with the LDAP Synthetic extension in SaaS. I saw some things that seem to be strange to me and I wanted to check if someone else has faced this.

When I create a configuration in the extension it creates a Synthetic monitor with the name defined in the extension. This monitor is visible in both the classic and new Synthetic apps. I am facing some issues though:

1) When I update the configuration in the extension this creates a new monitor on top of the already created one, which ends up in having more than one Synthetic LDAP monitor with the same name. If the configuration was initially failing the monitor associated with it shows failed status, while the new one, created upon changing the configuration shows OK status. I think Dynatrace should find a way to merge them (what I mean is that it updates the initially created monitor instead of creating a new one ontop of it).

2) When you need to remove a monitor (for example because of the duplication mentioned above) you are unable to do this via the new Synthetic app (it shows the following error: An error occurred while removing the monitors: Constraints violated.) If I try removing them from Synthetic classic it works like a charm.

3) Removing a configuration from the extension does not delete the associated Synthetic monitor.

Has anyone had such an experience?

All the best,
Georgi

Re: LDAP Synthetic extension

sujit_k_singh — Tue, 25 Aug 2026 02:22:09 GMT

Hi @Georgi_Vuldzhev

I am not sure my response would be helpful or not as this is bit old post, however,

This is known behavior with Extensions 2.0 (EEC) and protocol synthetic extensions like LDAP.

Duplicate Monitors: Modifying key configuration fields generates a new internal entity ID rather than updating the existing one in place. The old monitor becomes orphaned and retains its last polled state.

The new Synthetic app enforces entity relationship constraints that block direct deletion of extension-managed monitors. The Classic Synthetic app bypasses these checks, which is why deletion works there.

Extension Removal vs. Monitor Deletion: Deleting the configuration stops polling, but Dynatrace does not auto-purge the historical monitor entity.

Workaround: Use Classic Synthetic to manually delete stale or orphaned LDAP monitors whenever you update or remove the extension configuration.

Thanks,

Sujit

topic Re: LDAP Synthetic extension in Extensions

LDAP Synthetic extension

Re: LDAP Synthetic extension