# Avoid triggering problems for failure rates lasting less than 5 minutes

**URL:** <https://community.dynatrace.com/t/avoid-triggering-problems-for-failure-rates-lasting-less-than-5-minutes/35155>\
**Category:** Alerting\
**Tags:** problem-detection, problems-classic\
**Created:** [May 16, 2022, 4:27pm UTC](https://community.dynatrace.com/t/avoid-triggering-problems-for-failure-rates-lasting-less-than-5-minutes/35155 "2022-05-16T16:27:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mdouds](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@mdouds](https://community.dynatrace.com/u/mdouds)\
**Post date:** [May 16, 2022, 4:27pm UTC](https://community.dynatrace.com/t/avoid-triggering-problems-for-failure-rates-lasting-less-than-5-minutes/35155/1 "2022-05-16T16:27:53Z")

</div>

Dynatrace veterans are probably used to this type of question, and though we’ve been using Dynatrace since Appmon 3.0 days, I still have difficulties understand it.

We see a lot of problems with sporadic failures causing failure rate alerts. The failure rate itself might be&nbsp; above 50% (relative) for 10-20 seconds due to a single failure request. These generated high failure rate problems, so we enabled the anomaly detection setting to not alert us if the problem state was less than a minute.

After continuing to see problems detected, we increased to 5 minutes. Then we opened a support chat, and were told to try increasing it to 7 minutes due to the sliding 5-minute window:

 ![mdouds_0-1652717965978.png](https://global.discourse-cdn.com/dynatrace/original/3X/c/8/c8f0a84185994341e6b9a4e8a01dba550bc3dbfe.png)

We continue to see problems for failure rates lasting less than a minute. The problem might be open for 9 minutes…ok fine, it’s considered an “abnormal state” for longer than a minute, but why not have an anomaly detection setting based on the timespan of the actual failures?

![mdouds_1-1652718063886.png](https://global.discourse-cdn.com/dynatrace/original/3X/7/2/72daa00ea2ba436c7d481dc957fd1d408ce4d59b.png)

**What is the solution to prevent alerts if the failures lasted less than 1-2 minutes?**

---

<div class="post-metadata">

**Author:** ![techean](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/techean/32/227_2.png) [@techean](https://community.dynatrace.com/u/techean)\
**Post date:** [May 17, 2022, 3:36am UTC](https://community.dynatrace.com/t/avoid-triggering-problems-for-failure-rates-lasting-less-than-5-minutes/35155/2 "2022-05-17T03:36:17Z")

</div>

change the AI Detection alerts configuration through UI,

You can adjust the alert profile rules to not alert unless a problem is open for more then 7 mins and this should be able to solve your problem

---

<div class="post-metadata">

**Author:** ![mdouds](https://avatars.discourse-cdn.com/v4/letter/m/ce73a5/32.png) [@mdouds](https://community.dynatrace.com/u/mdouds)\
**Post date:** [May 23, 2022, 2:34pm UTC](https://community.dynatrace.com/t/avoid-triggering-problems-for-failure-rates-lasting-less-than-5-minutes/35155/3 "2022-05-23T14:34:53Z")

</div>

Hi&nbsp;[@techean](https://community.dynatrace.com/user/49581)&nbsp;,

The issue with this approach is that the “problem open time” does not match the span of the failure rate and seems a bit random. You could see a problem open for 8-15 minutes for 2 failed requests that actually spanned 20 seconds.