<?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 Anyone using (disk_queue_length) instead of %_disk_time for disk metrics??? in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Anyone-using-disk-queue-length-instead-of-disk-time-for-disk/m-p/485316#M8436</link>
    <description>&lt;P&gt;Hey Splunkers,&lt;/P&gt;

&lt;P&gt;Just wondering if anyone had some cool suggestions for better disk metrics&lt;/P&gt;

&lt;P&gt;We are currently using %_disk_time (among others) for performance monitoring for our hosts&lt;/P&gt;

&lt;P&gt;While it may be somewhat useful to know that drives are 100% busy, that fact in and of itself, is not as useful.&lt;/P&gt;

&lt;P&gt;I would expect that drives holding data would be 100% busy because the drive is being read from or written to almost all of the time, especially on some of our more heavily used systems &lt;/P&gt;

&lt;P&gt;Just from my own basic knowledge, that metric combined with “Average Disk Que Length”, would be more relevant.  If a disk is busy almost all of the time, and there is a large queue, the disk might be a bottleneck, and require further investigation.&lt;/P&gt;

&lt;P&gt;However, I imagine RAID configuration needs to be factored in (which I'm not sure about) -and I'm wondering how others are doing it.  Any help is much appreciated &lt;/P&gt;

&lt;P&gt;I'm currently playing around with it like this:&lt;/P&gt;

&lt;P&gt;index=windows sourcetype="PerfmonMk:LogicalDisk"&lt;BR /&gt;
| stats avg(Current_Disk_Queue_Length) as average by host instance&lt;BR /&gt;
| search average&amp;gt;1&lt;BR /&gt;
| sort - average&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 05:11:24 GMT</pubDate>
    <dc:creator>spluzer</dc:creator>
    <dc:date>2020-09-30T05:11:24Z</dc:date>
    <item>
      <title>Anyone using (disk_queue_length) instead of %_disk_time for disk metrics???</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Anyone-using-disk-queue-length-instead-of-disk-time-for-disk/m-p/485316#M8436</link>
      <description>&lt;P&gt;Hey Splunkers,&lt;/P&gt;

&lt;P&gt;Just wondering if anyone had some cool suggestions for better disk metrics&lt;/P&gt;

&lt;P&gt;We are currently using %_disk_time (among others) for performance monitoring for our hosts&lt;/P&gt;

&lt;P&gt;While it may be somewhat useful to know that drives are 100% busy, that fact in and of itself, is not as useful.&lt;/P&gt;

&lt;P&gt;I would expect that drives holding data would be 100% busy because the drive is being read from or written to almost all of the time, especially on some of our more heavily used systems &lt;/P&gt;

&lt;P&gt;Just from my own basic knowledge, that metric combined with “Average Disk Que Length”, would be more relevant.  If a disk is busy almost all of the time, and there is a large queue, the disk might be a bottleneck, and require further investigation.&lt;/P&gt;

&lt;P&gt;However, I imagine RAID configuration needs to be factored in (which I'm not sure about) -and I'm wondering how others are doing it.  Any help is much appreciated &lt;/P&gt;

&lt;P&gt;I'm currently playing around with it like this:&lt;/P&gt;

&lt;P&gt;index=windows sourcetype="PerfmonMk:LogicalDisk"&lt;BR /&gt;
| stats avg(Current_Disk_Queue_Length) as average by host instance&lt;BR /&gt;
| search average&amp;gt;1&lt;BR /&gt;
| sort - average&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 05:11:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Anyone-using-disk-queue-length-instead-of-disk-time-for-disk/m-p/485316#M8436</guid>
      <dc:creator>spluzer</dc:creator>
      <dc:date>2020-09-30T05:11:24Z</dc:date>
    </item>
  </channel>
</rss>

