<?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: Index Latency Summary in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82150#M832</link>
    <description>&lt;P&gt;Thanks Jeotron&lt;/P&gt;

&lt;P&gt;I was looking for a summary to speed up the search.  I need a report of the latency on one index for the last 24 hours so I am not interested in real time.  I did see the search from SOS thanks&lt;/P&gt;</description>
    <pubDate>Tue, 02 Apr 2013 17:22:20 GMT</pubDate>
    <dc:creator>hartfoml</dc:creator>
    <dc:date>2013-04-02T17:22:20Z</dc:date>
    <item>
      <title>Index Latency Summary</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82148#M830</link>
      <description>&lt;P&gt;I am calculating the index latency like this&lt;/P&gt;

&lt;P&gt;index=firewall | eval diff = _indextime - _time &lt;/P&gt;

&lt;P&gt;This is taking some time to run a 24 hour report as firewall logs are prolific.&lt;/P&gt;

&lt;P&gt;Does anyone know if the latency for indexes is in a summary index anywhere?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2013 16:39:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82148#M830</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-04-02T16:39:12Z</dc:date>
    </item>
    <item>
      <title>Re: Index Latency Summary</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82149#M831</link>
      <description>&lt;P&gt;Latencies are not stored anywhere. Your approach is correct, however you should be running this report in realtime using the all time (real time) dropdown option. This is to ensure that all incoming events are shown regardless of their extracted time stamp. Note that the latency measured here is affected by how old your events are when you expose them to Splunk. Alternatively, the SOS app includes a distributed indexing performance view that will show you realtime latency and is powered by this search&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* OR index=_internal
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;| eval latency=round((_indextime - _time),2)&lt;BR /&gt;
| eval seconds_elapsed=(time() - now())&lt;BR /&gt;
| eval secs=if(seconds_elapsed&amp;lt;0,"1",seconds_elapsed)&lt;BR /&gt;
| eval esize=((len(_raw)/1024))&lt;BR /&gt;
| eventstats max(secs) AS seconds&lt;BR /&gt;
| eventstats count AS ecount, sum(esize) AS sum_esize $type$&lt;BR /&gt;
| stats last(ecount) AS "event count"&lt;BR /&gt;
   last(eval(ecount/seconds)) AS eps&lt;BR /&gt;
   last(eval(sum_esize/seconds)) AS KBps&lt;BR /&gt;
   min(latency) AS "minimum latency (seconds)"&lt;BR /&gt;
   avg(latency) AS avglat&lt;BR /&gt;
   max(latency) AS "maximum latency (seconds)"&lt;BR /&gt;
   min(_time) AS oldestTime&lt;BR /&gt;
   max(_time) AS newestTime $type$&lt;BR /&gt;
| eval avglat=round(avglat,2)&lt;BR /&gt;
| eval eps=round(eps,2)&lt;BR /&gt;
| eval KBps=round(KBps,2)&lt;BR /&gt;
| convert timeformat="%m/%d/%Y %H:%M:%S" ctime(newestTime)&lt;BR /&gt;
| convert timeformat="%m/%d/%Y %H:%M:%S" ctime(oldestTime)&lt;BR /&gt;
| rename newestTime AS "Time stamp of newest event"&lt;BR /&gt;
   oldestTime AS "Time stamp of oldest event"&lt;BR /&gt;
   avglat AS "average latency (seconds)"&lt;BR /&gt;
   eps AS "events per second"&lt;BR /&gt;
   KBps AS "indexing rate (KBps)"&lt;/P&gt;

&lt;P&gt;Possible values for $type$: by index | by host | by source | by sourcetype | by splunk_server&lt;/P&gt;

&lt;P&gt;You can modify this search to suit your needs.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:39:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82149#M831</guid>
      <dc:creator>RicoSuave</dc:creator>
      <dc:date>2020-09-28T13:39:19Z</dc:date>
    </item>
    <item>
      <title>Re: Index Latency Summary</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82150#M832</link>
      <description>&lt;P&gt;Thanks Jeotron&lt;/P&gt;

&lt;P&gt;I was looking for a summary to speed up the search.  I need a report of the latency on one index for the last 24 hours so I am not interested in real time.  I did see the search from SOS thanks&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2013 17:22:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82150#M832</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-04-02T17:22:20Z</dc:date>
    </item>
    <item>
      <title>Re: Index Latency Summary</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82151#M833</link>
      <description>&lt;P&gt;By The Way, I left this one to run for quite a while and forgot about it.  It chewed up 10G in /opt/splunk/var/run/splunk/dispatch and caused me a small headache.  So don't leave it run too long:)&lt;/P&gt;

&lt;P&gt;Interesting data though! thanks!&lt;/P&gt;</description>
      <pubDate>Wed, 26 Mar 2014 15:10:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Index-Latency-Summary/m-p/82151#M833</guid>
      <dc:creator>glitchcowboy</dc:creator>
      <dc:date>2014-03-26T15:10:51Z</dc:date>
    </item>
  </channel>
</rss>

