<?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: Indexer I/O latency on reads and writes in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440674#M76816</link>
    <description>&lt;P&gt;Did you ever create alerts for disk performance from this app? I am trying to develop alerts based on different iostat metrics.&lt;/P&gt;</description>
    <pubDate>Sat, 18 Jan 2020 00:20:33 GMT</pubDate>
    <dc:creator>molinarf</dc:creator>
    <dc:date>2020-01-18T00:20:33Z</dc:date>
    <item>
      <title>Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440666#M76808</link>
      <description>&lt;P&gt;I am looking to show I/O latency on our indexers specific to reads and/or writes?  The Monitoring Console shows total IOPS but we'd like to go a little more granular than that.  We want to know if our disk latency is because of reads or writes on our hot/warm and cold mounts.  &lt;/P&gt;

&lt;P&gt;I'm looking at the introspection logs, at the fields indicated below, and it's not clear to me if &lt;STRONG&gt;reads_kb_ps&lt;/STRONG&gt; and &lt;STRONG&gt;writes_kb_ps&lt;/STRONG&gt; are the fields that will provide this data , based on their descriptions.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;avg_service_ms:&lt;/STRONG&gt; Average time requests caused the CPU to be in use, in milliseconds.&lt;BR /&gt;
&lt;STRONG&gt;avg_total_ms:&lt;/STRONG&gt;   Average queue + execution time for requests to be completed, in milliseconds.&lt;BR /&gt;
&lt;STRONG&gt;cpu_pct:&lt;/STRONG&gt;                    Percentage of time the CPU was servicing requests.&lt;BR /&gt;
&lt;STRONG&gt;device:&lt;/STRONG&gt;                 Device name (e.g., as listed under /dev on UNIX).&lt;BR /&gt;
&lt;STRONG&gt;fs_type:&lt;/STRONG&gt;                    Mounted device file system type.&lt;BR /&gt;
&lt;STRONG&gt;interval:&lt;/STRONG&gt;                   Interval over which sampling occurred, in seconds.&lt;BR /&gt;
&lt;STRONG&gt;mount_point:&lt;/STRONG&gt;    Mount point(s) of the underlying device.&lt;BR /&gt;
&lt;STRONG&gt;reads_kb_ps:&lt;/STRONG&gt;            Total number of kb read per second.&lt;BR /&gt;
&lt;STRONG&gt;reads_ps:&lt;/STRONG&gt;           Number of read requests per second.&lt;BR /&gt;
&lt;STRONG&gt;writes_kb_ps:&lt;/STRONG&gt;   Total number of kb written per second.&lt;BR /&gt;
&lt;STRONG&gt;writes_ps:&lt;/STRONG&gt;          Number of write requests per second.&lt;/P&gt;

&lt;P&gt;I've looked all over and haven't been able to find anything helpful.  I feel like someone else has to be doing this type of performance metric.  &lt;/P&gt;

&lt;P&gt;This is what the Monitoring Console has as the IOPS search.  How can I pick this apart to give me what I'm looking for?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=_introspection sourcetype=splunk_resource_usage component=IOStats host=&amp;lt;myhost&amp;gt; 
| eval mount_point = 'data.mount_point' 
| eval reads_ps = 'data.reads_ps' 
| eval writes_ps = 'data.writes_ps' 
| eval interval = 'data.interval' 
| eval op_count = (reads_ps + writes_ps) * interval 
| eval avg_service_ms = 'data.avg_service_ms' 
| eval avg_wait_ms = 'data.avg_total_ms' 
| eval cpu_pct = 'data.cpu_pct' 
| eval network_pct = 'data.network_pct' 
| timechart minspan=60s partial=f per_second(op_count) as iops, avg(data.cpu_pct) as avg_cpu_pct, avg(data.avg_service_ms) as avg_service_ms, avg(data.avg_total_ms) as avg_wait_ms, avg(data.network_pct) as avg_network_pct 
| eval iops = round(iops) 
| eval avg_cpu_pct = round(avg_cpu_pct) 
| eval avg_service_ms = round(avg_service_ms) 
| eval avg_wait_ms = round(avg_wait_ms) 
| eval avg_network_pct = round(avg_network_pct) 
| fields _time, iops avg_wait_ms 
| rename avg_wait_ms as "Wait Time (ms)"
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Sep 2020 21:43:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440666#M76808</guid>
      <dc:creator>bport15</dc:creator>
      <dc:date>2020-09-29T21:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440667#M76809</link>
      <description>&lt;P&gt;bport15,&lt;/P&gt;

&lt;P&gt;try to install "sysstat" package in your linux server and check read and writes by using  "sar" command&lt;/P&gt;

&lt;P&gt;you can use "iostat" and  "sar" commands  to find latency.&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 21:29:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440667#M76809</guid>
      <dc:creator>mpreddy</dc:creator>
      <dc:date>2018-10-22T21:29:16Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440668#M76810</link>
      <description>&lt;P&gt;Also refer to &lt;A href="https://answers.splunk.com/answers/690342/what-is-the-best-app-to-monitor-linux-in-splunk.html"&gt;What is the best app to monitor Linux in Splunk?&lt;/A&gt; , sar / iostat will work just fine but you might want to look at the linked answer so you can get this into Splunk easily and have prebuilt dashboards...&lt;/P&gt;</description>
      <pubDate>Mon, 22 Oct 2018 21:45:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440668#M76810</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2018-10-22T21:45:50Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440669#M76811</link>
      <description>&lt;P&gt;What is the latency you have - is it seconds, minutes? &lt;/P&gt;</description>
      <pubDate>Tue, 23 Oct 2018 11:31:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440669#M76811</guid>
      <dc:creator>ddrillic</dc:creator>
      <dc:date>2018-10-23T11:31:01Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440670#M76812</link>
      <description>&lt;P&gt;We're seeing a wide variety.  Some servers are showing 4-30ms on our hot/warm disk and other servers are showing up towards 2500ms on our hot/warm disk, with spikes above that.  I haven't even looked at our cold disk yet because the majority of our splunk users are hitting the warm buckets.  I'm looking to show historic values of i/o latency; not just what's currently going on.  &lt;/P&gt;</description>
      <pubDate>Wed, 24 Oct 2018 12:51:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440670#M76812</guid>
      <dc:creator>bport15</dc:creator>
      <dc:date>2018-10-24T12:51:11Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440671#M76813</link>
      <description>&lt;P&gt;Thanks mpreddy.  We can look on the box for current latency stats but I need to look at historic values, as well.  Previous 6 weeks, for example.  So I need to be able to graph something within Splunk.  &lt;/P&gt;</description>
      <pubDate>Wed, 24 Oct 2018 12:52:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440671#M76813</guid>
      <dc:creator>bport15</dc:creator>
      <dc:date>2018-10-24T12:52:41Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440672#M76814</link>
      <description>&lt;P&gt;@gjanders,&lt;BR /&gt;
I found an app and associated TA, SA that provides that kind of data. Look at the Metricator app&lt;/P&gt;

&lt;P&gt;&lt;A href="https://splunkbase.splunk.com/app/3947/"&gt;https://splunkbase.splunk.com/app/3947/&lt;/A&gt;&lt;BR /&gt;
&lt;A href="https://splunkbase.splunk.com/app/3948/"&gt;https://splunkbase.splunk.com/app/3948/&lt;/A&gt; (Technical Add On)&lt;BR /&gt;
&lt;A href="https://splunkbase.splunk.com/app/3949/"&gt;https://splunkbase.splunk.com/app/3949/&lt;/A&gt; (Support App)&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 18:03:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440672#M76814</guid>
      <dc:creator>molinarf</dc:creator>
      <dc:date>2020-01-17T18:03:31Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440673#M76815</link>
      <description>&lt;P&gt;I have been using this app for a long time and it's predecessor app nmon for splunk.&lt;/P&gt;

&lt;P&gt;Great app&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2020 23:40:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440673#M76815</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2020-01-17T23:40:10Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440674#M76816</link>
      <description>&lt;P&gt;Did you ever create alerts for disk performance from this app? I am trying to develop alerts based on different iostat metrics.&lt;/P&gt;</description>
      <pubDate>Sat, 18 Jan 2020 00:20:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440674#M76816</guid>
      <dc:creator>molinarf</dc:creator>
      <dc:date>2020-01-18T00:20:33Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer I/O latency on reads and writes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440675#M76817</link>
      <description>&lt;P&gt;No, I never created alerts from this one, good luck&lt;/P&gt;</description>
      <pubDate>Sun, 19 Jan 2020 23:18:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-I-O-latency-on-reads-and-writes/m-p/440675#M76817</guid>
      <dc:creator>gjanders</dc:creator>
      <dc:date>2020-01-19T23:18:29Z</dc:date>
    </item>
  </channel>
</rss>

