<?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: Staged Disk Alerting in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247644#M4553</link>
    <description>&lt;P&gt;Ahhh goddamnit, of course. Massive facepalm. Thank you Jaume&lt;/P&gt;</description>
    <pubDate>Fri, 07 Jun 2024 06:58:06 GMT</pubDate>
    <dc:creator>i_g</dc:creator>
    <dc:date>2024-06-07T06:58:06Z</dc:date>
    <item>
      <title>Staged Disk Alerting</title>
      <link>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247635#M4551</link>
      <description>&lt;P&gt;Good afternoon,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am in the process of creating staged alerting, but have ran into some problems. My intent is to raise an (ServiceNow P3) alert at 80% disk utilisation and a P2 at 90% utilisation.&lt;/P&gt;&lt;P&gt;Following on from some posts here about creating specific disk alerting profiles, I have disabled&amp;nbsp;&lt;SPAN&gt;Anomaly detection for infrastructure: Disk and created two metric events, one for 80 and one for 90%. They are both Metric Key alerts, using builtin:host.disk.usedPct with the threshold set respectively. The 80% is a Slowdown event type, the 90% an Error event type.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;I can generate the 80% with no problems from a dev server, however when filling a hard disk to greater than 90% for testing, the problems are linked into Multiple Infrastructure Problems and are raised in SNOW as a P3.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a way to overcome this please?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 05:35:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247635#M4551</guid>
      <dc:creator>i_g</dc:creator>
      <dc:date>2024-06-07T05:35:57Z</dc:date>
    </item>
    <item>
      <title>Re: Staged Disk Alerting</title>
      <link>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247643#M4552</link>
      <description>&lt;P&gt;Hello!&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yes there is an easy way to accomplish it. When creating the Metric key alert you can select a toggle that says "Allow merge", this will eliminate the behaviour of merging this Events into a single Problem.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="jaume_reverte_0-1717743332727.png" style="width: 459px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/20380iD2B1720EFE6D56FC/image-dimensions/459x333?v=v2" width="459" height="333" role="button" title="jaume_reverte_0-1717743332727.png" alt="jaume_reverte_0-1717743332727.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 06:56:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247643#M4552</guid>
      <dc:creator>jaume_reverte</dc:creator>
      <dc:date>2024-06-07T06:56:12Z</dc:date>
    </item>
    <item>
      <title>Re: Staged Disk Alerting</title>
      <link>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247644#M4553</link>
      <description>&lt;P&gt;Ahhh goddamnit, of course. Massive facepalm. Thank you Jaume&lt;/P&gt;</description>
      <pubDate>Fri, 07 Jun 2024 06:58:06 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Staged-Disk-Alerting/m-p/247644#M4553</guid>
      <dc:creator>i_g</dc:creator>
      <dc:date>2024-06-07T06:58:06Z</dc:date>
    </item>
  </channel>
</rss>

