<?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: Davis® Anomaly Detection -Manual suppress problem, Open a new one if issue still exist in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/258074#M4941</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/71933"&gt;@Sachinpai&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;Not sure why you want a problem to open when you have closed it manually. Davis wouldn't do that when it Identifies a problem let's say you consider error when a certain log record occurs more than 100 times in an hour then Davis creates problem based on the "Static Threshold" that you have created. Once it crosses 100 unless it comes down and goes up again it is the same problem. When you close it manually Davis understands that you want to ignore this issue or you have done something that will resolve this eventually.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;All the theory aside, if you really want this to happen I suggest to use workflows and combine it with events API to create problems manually. Do remember to add this tag as property&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dt.event.allow_frequent_issue_detection:false &lt;/LI-CODE&gt;&lt;P&gt;This allows davis not to suppress problems even when they occur frequently. This may or may not work on Davis Anomaly Detector App.&lt;/P&gt;</description>
    <pubDate>Thu, 03 Oct 2024 19:04:27 GMT</pubDate>
    <dc:creator>Maheedhar_T</dc:creator>
    <dc:date>2024-10-03T19:04:27Z</dc:date>
    <item>
      <title>Davis® Anomaly Detection -Manual suppress problem, Open a new one if issue still exist</title>
      <link>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/256865#M4874</link>
      <description>&lt;P&gt;We created static threshold anomaly detector event using new named "App Davis® Anomaly Detection". We are successfully able to create problem if DQL result violate threshold. Our query is if problem is manually closed, and issue still exist then new problem is not opening. We tried option of adding property dt.event.suppress_problem false in the event property but still didn't open new problem. is there a way this can be done?&lt;/P&gt;</description>
      <pubDate>Mon, 23 Sep 2024 20:40:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/256865#M4874</guid>
      <dc:creator>Sachinpai</dc:creator>
      <dc:date>2024-09-23T20:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: Davis® Anomaly Detection -Manual suppress problem, Open a new one if issue still exist</title>
      <link>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/258074#M4941</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/71933"&gt;@Sachinpai&lt;/a&gt;&amp;nbsp;,&lt;BR /&gt;Not sure why you want a problem to open when you have closed it manually. Davis wouldn't do that when it Identifies a problem let's say you consider error when a certain log record occurs more than 100 times in an hour then Davis creates problem based on the "Static Threshold" that you have created. Once it crosses 100 unless it comes down and goes up again it is the same problem. When you close it manually Davis understands that you want to ignore this issue or you have done something that will resolve this eventually.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;All the theory aside, if you really want this to happen I suggest to use workflows and combine it with events API to create problems manually. Do remember to add this tag as property&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;dt.event.allow_frequent_issue_detection:false &lt;/LI-CODE&gt;&lt;P&gt;This allows davis not to suppress problems even when they occur frequently. This may or may not work on Davis Anomaly Detector App.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Oct 2024 19:04:27 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/258074#M4941</guid>
      <dc:creator>Maheedhar_T</dc:creator>
      <dc:date>2024-10-03T19:04:27Z</dc:date>
    </item>
    <item>
      <title>Re: Davis® Anomaly Detection -Manual suppress problem, Open a new one if issue still exist</title>
      <link>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/259036#M4991</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/71933"&gt;@Sachinpai&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for sharing your concern.&lt;/P&gt;&lt;P&gt;Kindly find the attached resources to figure out the full picture regarding the correlation between Davis &amp;amp;&amp;amp; Anomaly detection ,.. etc:&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/detect-problems-with-logs" target="_self"&gt;detect-problems-with-logs&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/frequent-issues" target="_self"&gt;frequent-issues&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/davis-ai-anomaly-detection-app" target="_self"&gt;davis-ai-anomaly-detection-app&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/problem-detection-sensitivity" target="_self"&gt;problem-detection-sensitivity&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/platform/davis-ai" target="_self"&gt;davis-ai&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/davis-ai-use-cases-anomaly-detection" target="_self"&gt;davis-ai-use-cases-anomaly-detection&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;LI&gt;&lt;A href="https://docs.dynatrace.com/docs/shortlink/davis-ai-root-cause-concepts" target="_self"&gt;davis-ai-root-cause-concepts&lt;/A&gt;&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;Simply&lt;/STRONG&gt;:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If you close the problem manually, So Davis AI will understand that the problem was triggered for threshold violation and the intended admin ignores this issue for the provided reason in the comment section.&lt;/LI&gt;&lt;LI&gt;If the problem is opened, the new events will be added automatically to the current opened problem.&lt;/LI&gt;&lt;LI&gt;Dynatrace won't raise a problem alert for the entity that impacted by the frequent issue, but you will be able to see the section of the frequent issues contain the most repeated issue.&lt;/LI&gt;&lt;LI&gt;Dynatrace will trigger an alert when the problem severity increases.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hoping the shared resources add value.&lt;/P&gt;&lt;P&gt;KR,&lt;/P&gt;&lt;P&gt;Peter.&lt;/P&gt;</description>
      <pubDate>Sun, 13 Oct 2024 19:11:59 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Davis-Anomaly-Detection-Manual-suppress-problem-Open-a-new-one/m-p/259036#M4991</guid>
      <dc:creator>Peter_Youssef</dc:creator>
      <dc:date>2024-10-13T19:11:59Z</dc:date>
    </item>
  </channel>
</rss>

