<?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: Health status of IOWait is read!! in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/584286#M11521</link>
    <description>&lt;P&gt;After using the health reporter analyzer for a few weeks, I will agree, it really doesn't seem to be very accurate in a distributed/clustered environment.&lt;/P&gt;&lt;P&gt;I have massively overpowered environments that are still getting IOWait alerts even after raising the thresholds.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've also seen suggestions to raise the suppression status. I am trying it.&lt;/P&gt;&lt;PRE&gt;suppress_status_update_ms = 30000
* Default: 300.&lt;/PRE&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.4/Admin/Healthconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.4/Admin/Healthconf&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 09 Feb 2022 13:50:42 GMT</pubDate>
    <dc:creator>_joe</dc:creator>
    <dc:date>2022-02-09T13:50:42Z</dc:date>
    <item>
      <title>Why is the health status of IOWait red?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565902#M9870</link>
      <description>&lt;P&gt;After I successfully installed Splunk Enterprise and I'd added some data I tried to do some searching, but there was an issue with searching, and the intended result doesn't appear at all. I think this is due to the red health status for IOWait as shown below, so how could solve this issue?&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="45.png" style="width: 400px;"&gt;&lt;img src="https://community.splunk.com/t5/image/serverpage/image-id/15845i10A567E04338CE07/image-size/medium?v=v2&amp;amp;px=400" role="button" title="45.png" alt="45.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Feb 2022 00:50:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565902#M9870</guid>
      <dc:creator>aateeq</dc:creator>
      <dc:date>2022-02-10T00:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565904#M9872</link>
      <description>&lt;P&gt;Hello &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/238053"&gt;@aateeq&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;This is a disk performance issue. Looks like the IO of the disk, where you've installed Splunk is very low. You'll have to check and v&lt;SPAN&gt;erify the throuput of your disks, Splunk requires at least 800 iops. The more the better. You can use tools like bonnie++ to measure the IO of a disk.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Also, please make sure that there's enough space on the partition, where Splunk is installed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Hope this helps.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;S&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;***If this helped, please accept it as a solution. It helps others to find the solution for similar issues quickly.***&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 04 Sep 2021 12:12:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565904#M9872</guid>
      <dc:creator>shivanshu1593</dc:creator>
      <dc:date>2021-09-04T12:12:37Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565906#M9873</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/61125"&gt;@shivanshu1593&lt;/a&gt;&amp;nbsp; Thanks for your reply.&lt;/P&gt;&lt;P&gt;I installed the Linux machine in a Vbox with 40G disk space, so I think I have enough disk space for Splunk. But, regarding the throughput of the disk how can I check it and increase it to more than 800 iops؟&lt;/P&gt;</description>
      <pubDate>Sat, 04 Sep 2021 12:44:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565906#M9873</guid>
      <dc:creator>aateeq</dc:creator>
      <dc:date>2021-09-04T12:44:49Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565907#M9874</link>
      <description>&lt;P&gt;You can go through the following link and use either dd or bonnie++ to check the IOPS.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.jamescoyle.net/how-to/599-benchmark-disk-io-with-dd-and-bonnie" target="_blank"&gt;https://www.jamescoyle.net/how-to/599-benchmark-disk-io-with-dd-and-bonnie&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;S&lt;/P&gt;</description>
      <pubDate>Sat, 04 Sep 2021 13:08:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/565907#M9874</guid>
      <dc:creator>shivanshu1593</dc:creator>
      <dc:date>2021-09-04T13:08:51Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/580935#M11156</link>
      <description>&lt;P&gt;Go to&amp;nbsp;&lt;STRONG&gt;Settings &amp;gt; Health report manager&amp;nbsp;&lt;/STRONG&gt;and edit the threshold for IOWait. Double the thresholds you are currently hitting.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.3/DMC/Configurefeaturemonitoring#Disable_a_feature" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.3/DMC/Configurefeaturemonitoring#Disable_a_feature&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 13 Jan 2022 12:32:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/580935#M11156</guid>
      <dc:creator>_joe</dc:creator>
      <dc:date>2022-01-13T12:32:45Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/584286#M11521</link>
      <description>&lt;P&gt;After using the health reporter analyzer for a few weeks, I will agree, it really doesn't seem to be very accurate in a distributed/clustered environment.&lt;/P&gt;&lt;P&gt;I have massively overpowered environments that are still getting IOWait alerts even after raising the thresholds.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've also seen suggestions to raise the suppression status. I am trying it.&lt;/P&gt;&lt;PRE&gt;suppress_status_update_ms = 30000
* Default: 300.&lt;/PRE&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.4/Admin/Healthconf" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.4/Admin/Healthconf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 09 Feb 2022 13:50:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/584286#M11521</guid>
      <dc:creator>_joe</dc:creator>
      <dc:date>2022-02-09T13:50:42Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599059#M12635</link>
      <description>&lt;P&gt;I'm using Azure Premium SSD which should have max IOPS of 20,000, according to the documentation, but I'll run a test to see some real-life results.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 12:35:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599059#M12635</guid>
      <dc:creator>vzabawski</dc:creator>
      <dc:date>2022-05-24T12:35:37Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599061#M12636</link>
      <description>&lt;P&gt;Have you by any chance upgraded to 8.2.5 if yes then IOPS values are a bit sensitive.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 12:39:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599061#M12636</guid>
      <dc:creator>SinghK</dc:creator>
      <dc:date>2022-05-24T12:39:05Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599091#M12639</link>
      <description>&lt;P&gt;Yes, I've upgraded from 7.x to 8.2.x and after that I've started receiving those notifications.&lt;/P&gt;&lt;P&gt;I've measured iops and seems like everything is fine:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;fiotest: (groupid=0, jobs=1): err= 0: pid=29: Tue May 24 13:40:16 2022
read: IOPS=1796, BW=7186KiB/s (7358kB/s)(6141MiB/875157msec)
bw ( KiB/s): min= 5584, max= 9976, per=100.00%, avg=7192.71, stdev=565.38, samples=1748
iops : min= 1396, max= 2494, avg=1798.08, stdev=141.33, samples=1748
write: IOPS=599, BW=2400KiB/s (2457kB/s)(2051MiB/875157msec); 0 zone resets
bw ( KiB/s): min= 1888, max= 2885, per=100.00%, avg=2401.51, stdev=73.89, samples=1748
iops : min= 472, max= 721, avg=600.34, stdev=18.47, samples=1748
cpu : usr=0.89%, sys=2.59%, ctx=533118, majf=0, minf=6
IO depths : 1=0.1%, 2=0.1%, 4=0.1%, 8=0.1%, 16=0.1%, 32=0.1%, &amp;gt;=64=100.0%
submit : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.0%, &amp;gt;=64=0.0%
complete : 0=0.0%, 4=100.0%, 8=0.0%, 16=0.0%, 32=0.0%, 64=0.1%, &amp;gt;=64=0.0%
issued rwts: total=1572145,525007,0,0 short=0,0,0,0 dropped=0,0,0,0
latency : target=0, window=0, percentile=100.00%, depth=64&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 24 May 2022 14:35:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599091#M12639</guid>
      <dc:creator>vzabawski</dc:creator>
      <dc:date>2022-05-24T14:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599092#M12640</link>
      <description>&lt;P&gt;What version of splunk are you on?&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 14:42:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599092#M12640</guid>
      <dc:creator>SinghK</dc:creator>
      <dc:date>2022-05-24T14:42:26Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599093#M12641</link>
      <description>&lt;P&gt;i have seen this in other environments too.. let me see if i can get the attention to this, seems like a never ending issue.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 14:49:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599093#M12641</guid>
      <dc:creator>SinghK</dc:creator>
      <dc:date>2022-05-24T14:49:29Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599097#M12643</link>
      <description>&lt;P&gt;Splunk 8.2.5, but I'm getting this alert starting from Splunk 8.1.6 (if I'm not mistaken).&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 14:52:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599097#M12643</guid>
      <dc:creator>vzabawski</dc:creator>
      <dc:date>2022-05-24T14:52:55Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599099#M12645</link>
      <description>&lt;P&gt;Give me few mins I am checking how can we escalate it .&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 14:54:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599099#M12645</guid>
      <dc:creator>SinghK</dc:creator>
      <dc:date>2022-05-24T14:54:35Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599100#M12646</link>
      <description>&lt;P&gt;I'd suggest checking the actual IOPS using dd or Bonnie ++. The issue almost certainly is due to the low IOPS. Why is it happening can be checked by these tools.&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.jamescoyle.net/how-to/599-benchmark-disk-io-with-dd-and-bonnie" target="_blank" rel="nofollow noopener noreferrer"&gt;https://www.jamescoyle.net/how-to/599-benchmark-disk-io-with-dd-and-bonnie&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 14:55:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599100#M12646</guid>
      <dc:creator>shivanshu1593</dc:creator>
      <dc:date>2022-05-24T14:55:33Z</dc:date>
    </item>
    <item>
      <title>Re: Health status of IOWait is read!!</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599104#M12647</link>
      <description>&lt;P&gt;I have reported this as a bug lets see what they say.&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 15:05:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Why-is-the-health-status-of-IOWait-red/m-p/599104#M12647</guid>
      <dc:creator>SinghK</dc:creator>
      <dc:date>2022-05-24T15:05:23Z</dc:date>
    </item>
  </channel>
</rss>

