topic Re: Davis anomaly detector problem into management zone in Alerting

Assign Davis anomaly detector problem into management zone

Pablo2 — Thu, 18 Dec 2025 10:16:07 GMT

I need to put a problem we generated in the Davis Anomaly Detector into a management zone. The problem is that the alert comes from a business event and does not recognise any entity as a problem. The environment appears, and then we cannot relate the entity to any MZ.

Re: Davis anomay detector problem into management zone

dannemca — Thu, 04 Sep 2025 13:00:58 GMT

Could you show us how is the alerting condition for this business event?

Re: Davis anomay detector problem into management zone

Pablo2 — Thu, 04 Sep 2025 13:20:24 GMT

Re: Davis anomaly detector problem into management zone

shubham1413 — Sun, 07 Dec 2025 04:57:42 GMT

Hi @Pablo2 , can you confirm if this issue is resolved? If it is resolved, could you please provide the solution and explain how you configured sending problems for a specific MZ?

Re: Davis anomaly detector problem into management zone

sujit_k_singh — Tue, 09 Dec 2025 03:48:50 GMT

Hello @Pablo2,

You can assign Davis anomaly detector problems to a Management Zone only if the event is tied to a valid entity that belongs to that zone. Business events without entity context won’t map to any MZ.
Management Zones in Dynatrace are entity-based. They filter problems based on the entities involved (hosts, services, process groups, etc.). If your business event doesn’t reference a valid entity, Dynatrace can’t associate the resulting problem with any MZ — even if the environment is visible.

In your event template, the dt.source_entity is set to {dims:dt.source_entity}. This works only if the metric or DQL query includes a valid entity dimension.

To ensure the problem appears in a Management Zone:Use a dimension like {dims:dt.entity.process_group_instance} or {dims:dt.entity.service} depending on your metric scope. Check that the entity referenced in dt.source_entity is tagged or scoped into the MZ you want, you can use autotagging rules to ensure consistent MZ inclusion.

Thanks,

Tijust

Re: Davis anomaly detector problem into management zone

Maheedhar_T — Tue, 09 Dec 2025 05:45:00 GMT

Hi @Pablo2 ,
What you can do in this case is create a Custom Device (Name it as <Application Z- Your Application Name Here> or tag with your application name) and when an error occurs in your bizevent case, tie this to the Custom Device that's created using dt.source_entity property.
In the snippet you shared it's the first property. In the value you can remove {dims:dt.source_entity} and give the Custom Device ID that you created.
Then in the management Zones, add a rule that Custom Device with Tag <Application Z> belongs to this management zone.

Regards,
@Maheedhar_T