topic Re: dt.davis.analysis_trigger_delay - evaluation in DQL

dt.davis.analysis_trigger_delay - evaluation

munawarhossain3 — Fri, 03 Apr 2026 12:08:04 GMT

Hello,

I've created a process availability alert and want to delay it by 1 minute.

So, I added property as (enclosed, image 1 and 2).

Now, which is the right way (1 or 2)?

How Dynatrace is going to evaluate this?

Thanks

Munawar

Re: dt.davis.analysis_trigger_delay - evaluation

AntonPineiro — Fri, 03 Apr 2026 12:11:00 GMT

Hi,

Not sure how you have configured that alert, but I would add delay in the alerting profile.

Best regards

Re: dt.davis.analysis_trigger_delay - evaluation

munawarhossain3 — Fri, 03 Apr 2026 12:18:39 GMT

Hello,

That's a common AP.

So, I cannot touch that. So, added a property on the process availability page.

Thanks

Re: dt.davis.analysis_trigger_delay - evaluation

t_pawlak — Sun, 05 Apr 2026 08:54:13 GMT

Hi,
Dynatrace expects a time value with unit for this property: dt.davis.analysis_trigger_delay.

So:

1m is valid, interpreted as 1 minute
1 - invalid/ignored or treated incorrectly (no unit --> undefined behavior)

In Dynatrace evaluates it, Davis waits the specified delay before triggering problem analysis
In your case: waits 1 minute after issue detection
If condition disappears within that time -> no problem created

This is not the same as alerting profile delay (it delays Davis analysis itself, not notifications).