Alerting with custom topology & dynatrace.davis.anomalydetection

RafaelF — Fri, 13 Mar 2026 08:29:14 GMT

Good morning.

I have an use case where I want to alert on custom topology (one-to-many relationships) while making use of Davis to "smartly" merge my alerts and somewhat understand root cause.

Consider the following example:

my.metric.failure_rate,parent="Parent1",child="Child1" 5
my.metric.failure_rate,parent="Parent1",child="Child2" 10

Where topology is defined as:

Parent1 called_by child1
Parent1 called_by child2

The idea is that the problem can be limited to the scope of the child or can be more broad, if both parent and child are violating the defined threshold they I should be able to merge both events into a single problem, no?

I have tried using some of the dt.* configurations for the event but without the expected result.

event.type="AVAILABILITY_EVENT"
dt.davis.is_merging_allowed="true"
dt.davis.analysis_time_budget=240
dt.davis.analysis_trigger_delay=120
dt.davis.is_entity_remapping_allowed="false" // Set to true on child
dt.davis.preferred_entity_type="parent"

Note that my metric has a delay and is not ingested every minute, I have set the query offset and delay accordingly.

Anyone has been able to do something similar? Is there another approach for this?

Best regards,
Rafael

Re: Alerting with custom topology & dynatrace.davis.anomalydetection

Julius_Loman — Thu, 12 Mar 2026 13:33:52 GMT

AFAIK (I'm not aware of any changes) Dynatrace Intelligence (ex. Davis AI) follows only runs_on relations on custom devices. See this post .

@wolfgang_beer are there any updates since 2023 when it comes to custom entities and following relations in root cause analysis?

topic Re: Alerting with custom topology & dynatrace.davis.anomalydetection in Alerting

Alerting with custom topology & dynatrace.davis.anomalydetection

Re: Alerting with custom topology & dynatrace.davis.anomalydetection