topic Re: Custom Entity Integration in Davis Anomaly Detection in Alerting

Custom Entity Integration in Davis Anomaly Detection

AK — Mon, 08 Dec 2025 07:02:27 GMT

Hi Folks,

Is there a way to pass a custom entity in "Davis anomaly detection" so that it appears as the impacted entity when an problem is generated?

I've attempted to use dt.davis.is_entity_remapping_allowed set to false in the event description, along with dt.source_entity as my custom entity (e.g., host@process), but this approach doesn't seem to be working.

Has anyone successfully managed to do this?

Regards,
AK

Re: Custom Entity Integration in Davis Anomaly Detection

sia_h — Sat, 06 Dec 2025 09:16:17 GMT

Yes, but dt.source_entity should be a single entity. E.g. the value should be {dims:dt.entity.process_group_instance} or hardcoded CUSTOM_DEVICE-A5C88F64EE123123.

Re: Custom Entity Integration in Davis Anomaly Detection

sujit_k_singh — Tue, 09 Dec 2025 03:40:12 GMT

Hello,

@sia_h Thanks for clarifying! Yes, dt.source_entity needs to point to a single, valid entity. That can be either a dimension reference like {dims:dt.entity.process_group_instance} if event is scoped to a process group instance, or a hardcoded entity ID such as CUSTOM_DEVICE-XXXX if you’ve registered a custom device in Dynatrace.

@AK The key is that the entity you reference must already exist in Dynatrace’s topology — otherwise Davis will ignore it and remap to the closest known entity. If you also set dt.davis.is_entity_remapping_allowed=false, Davis will keep the problem tied to that entity once it’s valid. So the approach works, but only if the entity is properly defined in Dynatrace first.

Davis AI — Dynatrace Docs