<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to avoid triggering problems for failure rates lasting less than 5 minutes? in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/187053#M3002</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/49581"&gt;@techean&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 23 May 2022 14:34:53 GMT</pubDate>
    <dc:creator>mdouds</dc:creator>
    <dc:date>2022-05-23T14:34:53Z</dc:date>
    <item>
      <title>Avoid triggering problems for failure rates lasting less than 5 minutes</title>
      <link>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/186543#M2991</link>
      <description>&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We see a lot of problems with sporadic failures causing failure rate alerts. The failure rate itself might be&amp;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.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mdouds_0-1652717965978.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/5677i8CB1DC91E6442CC1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mdouds_0-1652717965978.png" alt="mdouds_0-1652717965978.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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?&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="mdouds_1-1652718063886.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/5678iBE77CC7784B78894/image-size/medium?v=v2&amp;amp;px=400" role="button" title="mdouds_1-1652718063886.png" alt="mdouds_1-1652718063886.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;What is the solution to prevent alerts if the failures lasted less than 1-2 minutes?&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Aug 2024 08:21:28 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/186543#M2991</guid>
      <dc:creator>mdouds</dc:creator>
      <dc:date>2024-08-13T08:21:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid triggering problems for failure rates lasting less than 5 minutes?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/186554#M2992</link>
      <description>&lt;P&gt;&lt;SPAN&gt;change the AI Detection alerts configuration through UI,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;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&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2022 03:36:17 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/186554#M2992</guid>
      <dc:creator>techean</dc:creator>
      <dc:date>2022-05-17T03:36:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to avoid triggering problems for failure rates lasting less than 5 minutes?</title>
      <link>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/187053#M3002</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/49581"&gt;@techean&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;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.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 23 May 2022 14:34:53 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Avoid-triggering-problems-for-failure-rates-lasting-less-than-5/m-p/187053#M3002</guid>
      <dc:creator>mdouds</dc:creator>
      <dc:date>2022-05-23T14:34:53Z</dc:date>
    </item>
  </channel>
</rss>

