<?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: Test Alerting in Dynatrace SaaS in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124011#M1868</link>
    <description>&lt;P&gt;That very much depends on what kind of situation you want to test. If its a simple CPU spike, its just necessary to use more than 95% CPU over 3 minutes and you get a problem opened. &lt;/P&gt;&lt;P&gt;For service baselining its at lest necessary to run the service for more than 5hours with continous load above 10 requests/min. You can also reduce that amount by changing the service anomaly detection config. &lt;/P&gt;&lt;P&gt;Best greetings,&lt;/P&gt;&lt;P&gt;Wolfgang &lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 07 Oct 2019 12:06:21 GMT</pubDate>
    <dc:creator>wolfgang_beer</dc:creator>
    <dc:date>2019-10-07T12:06:21Z</dc:date>
    <item>
      <title>Test Alerting in Dynatrace SaaS</title>
      <link>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124010#M1867</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;is there a way to reproduce and test alerting in Dynatrace SaaS? During Service Acceptance we have to perform a necessary "smoke testing" of deployed monitoring &amp;amp; alerting. We tried to simulate different scenarios on monitored host but Dynatrace SaaS didn't fire an alert at all. &lt;/P&gt;&lt;P&gt;Can you provide a guide how we can test different scenarios because AI module identifies our attempts?&lt;/P&gt;&lt;P&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Konstantin&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 07 Oct 2019 11:51:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124010#M1867</guid>
      <dc:creator>Konstantin_Mavr</dc:creator>
      <dc:date>2019-10-07T11:51:04Z</dc:date>
    </item>
    <item>
      <title>Re: Test Alerting in Dynatrace SaaS</title>
      <link>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124011#M1868</link>
      <description>&lt;P&gt;That very much depends on what kind of situation you want to test. If its a simple CPU spike, its just necessary to use more than 95% CPU over 3 minutes and you get a problem opened. &lt;/P&gt;&lt;P&gt;For service baselining its at lest necessary to run the service for more than 5hours with continous load above 10 requests/min. You can also reduce that amount by changing the service anomaly detection config. &lt;/P&gt;&lt;P&gt;Best greetings,&lt;/P&gt;&lt;P&gt;Wolfgang &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 07 Oct 2019 12:06:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124011#M1868</guid>
      <dc:creator>wolfgang_beer</dc:creator>
      <dc:date>2019-10-07T12:06:21Z</dc:date>
    </item>
    <item>
      <title>Re: Test Alerting in Dynatrace SaaS</title>
      <link>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124012#M1869</link>
      <description>Testing is more related to Service Availability (stopped / crashed of different services).&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Konstantin&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 07 Oct 2019 12:12:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Test-Alerting-in-Dynatrace-SaaS/m-p/124012#M1869</guid>
      <dc:creator>Konstantin_Mavr</dc:creator>
      <dc:date>2019-10-07T12:12:18Z</dc:date>
    </item>
  </channel>
</rss>

