<?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: Low disk space - problem creation suppressed in Alerting</title>
    <link>https://community.dynatrace.com/t5/Alerting/Low-disk-space-problem-creation-suppressed/m-p/278094#M5669</link>
    <description>&lt;P&gt;HI all&lt;/P&gt;&lt;P&gt;Got answers from support:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;D&lt;SPAN&gt;isabling the config for the timeout period (I believe 15 minutes) should cause the ongoing event to timeout. Afterwards, a new problem would be created.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Event Rest API with&lt;EM&gt;&lt;STRONG&gt; eventSelector=&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;EM&gt;&lt;STRONG&gt;suppressProblem(true),eventType("OSI_LOW_DISK_SPACE")&lt;/STRONG&gt;&lt;/EM&gt; will do the job&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Yos&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 27 May 2025 13:43:02 GMT</pubDate>
    <dc:creator>Yosi_Neuman</dc:creator>
    <dc:date>2025-05-27T13:43:02Z</dc:date>
    <item>
      <title>Low disk space - problem creation suppressed</title>
      <link>https://community.dynatrace.com/t5/Alerting/Low-disk-space-problem-creation-suppressed/m-p/277926#M5666</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;
&lt;P&gt;We found out that when there is an on going problem on low disk space and we raise the limit (lets say from 2% to 5%) the problem is closed on the spot and the disk is marked as&amp;nbsp;&lt;EM&gt;problem creation suppressed &lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Yosi_Neuman_0-1748002858512.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/28178iB65CEF6DC8AAD75E/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Yosi_Neuman_0-1748002858512.png" alt="Yosi_Neuman_0-1748002858512.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;Our questions are:&lt;/P&gt;
&lt;P&gt;1. Is there another way to remove this state form disk beside changing the limit?&lt;/P&gt;
&lt;P&gt;2. Which rest api we need to utilize in order to collect all disks that are in this state?&lt;/P&gt;
&lt;P&gt;Thanks in advance for your inputs&lt;/P&gt;
&lt;P&gt;Yos&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 May 2025 06:11:38 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Low-disk-space-problem-creation-suppressed/m-p/277926#M5666</guid>
      <dc:creator>Yosi_Neuman</dc:creator>
      <dc:date>2025-05-26T06:11:38Z</dc:date>
    </item>
    <item>
      <title>Re: Low disk space - problem creation suppressed</title>
      <link>https://community.dynatrace.com/t5/Alerting/Low-disk-space-problem-creation-suppressed/m-p/278094#M5669</link>
      <description>&lt;P&gt;HI all&lt;/P&gt;&lt;P&gt;Got answers from support:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;D&lt;SPAN&gt;isabling the config for the timeout period (I believe 15 minutes) should cause the ongoing event to timeout. Afterwards, a new problem would be created.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Event Rest API with&lt;EM&gt;&lt;STRONG&gt; eventSelector=&lt;/STRONG&gt;&lt;/EM&gt;&lt;/SPAN&gt;&lt;EM&gt;&lt;STRONG&gt;suppressProblem(true),eventType("OSI_LOW_DISK_SPACE")&lt;/STRONG&gt;&lt;/EM&gt; will do the job&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;Yos&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 May 2025 13:43:02 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Alerting/Low-disk-space-problem-creation-suppressed/m-p/278094#M5669</guid>
      <dc:creator>Yosi_Neuman</dc:creator>
      <dc:date>2025-05-27T13:43:02Z</dc:date>
    </item>
  </channel>
</rss>

