<?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 Latency in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81239#M16762</link>
    <description>&lt;P&gt;This worked for me.  Not sure why the table didn't like to display the raw indextime.&lt;/P&gt;

&lt;P&gt;source=/var/log/* | eval time=_time | eval itime=_indextime | eval latency=(itime - time) | table time,itime,latency,_raw&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 13:39:10 GMT</pubDate>
    <dc:creator>steve</dc:creator>
    <dc:date>2020-09-28T13:39:10Z</dc:date>
    <item>
      <title>Indexer Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81236#M16759</link>
      <description>&lt;P&gt;I have one heavy weight forwarder that is collecting from over 600 Universal Forwarder.  I have syslog-ng installed on HW Forwarder collecting syslog to folder and reading folder with Splunk.&lt;/P&gt;

&lt;P&gt;I am seeing (in SOS) an index latency of more than 1000 seconds on some of the indexes.&lt;BR /&gt;
Where to look next for the cause is a problem????&lt;BR /&gt;
How can i see if it is the indexers or my HW forwarder that is the bottle-neck.&lt;/P&gt;

&lt;P&gt;I think it is the indexers but were to look to see where the issue is on the 3 indexers???&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2013 22:16:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81236#M16759</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-04-01T22:16:56Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81237#M16760</link>
      <description>&lt;P&gt;You could do something like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;some search | eval diff = _indextime - _time | where diff &amp;gt; some value
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and go from there to see patterns of offending sources, hosts, splunk_servers, whatever.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Apr 2013 22:52:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81237#M16760</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-04-01T22:52:00Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81238#M16761</link>
      <description>&lt;P&gt;Martin thanks for the help.  I tried this search:&lt;BR /&gt;
index=firewall | eval diff = _indextime - _time | where diff &amp;gt; 890 | table _indextime _time&lt;/P&gt;

&lt;P&gt;I could not find the _indextime and the search would only find all results or no results as i increased the greater than number.  I wanted to see the diff between the index time and the time so I added the table command but all that showed was the time not the indextime.  Do you know how I can see the "index time"?&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2013 14:09:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81238#M16761</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-04-02T14:09:01Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81239#M16762</link>
      <description>&lt;P&gt;This worked for me.  Not sure why the table didn't like to display the raw indextime.&lt;/P&gt;

&lt;P&gt;source=/var/log/* | eval time=_time | eval itime=_indextime | eval latency=(itime - time) | table time,itime,latency,_raw&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:39:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81239#M16762</guid>
      <dc:creator>steve</dc:creator>
      <dc:date>2020-09-28T13:39:10Z</dc:date>
    </item>
    <item>
      <title>Re: Indexer Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81240#M16763</link>
      <description>&lt;P&gt;I found this article that talked about how to see the index time&lt;/P&gt;

&lt;P&gt;&lt;A href="http://splunk-base.splunk.com/answers/64388/is-_indextime-deprecated"&gt;http://splunk-base.splunk.com/answers/64388/is-_indextime-deprecated&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;I used the suggestion from Martin to right this search&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=firewall | eval diff = _indextime - _time | where diff &amp;gt; 0 | rename _indextime AS indxtime | rename _indextime AS indxtime | convert timeformat="%m/%d/%y %H:%M:%S" ctime(indxtime) | table _time indxtime diff
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;this alowed me to see the diff between the _time and the _indextime&lt;/P&gt;

&lt;P&gt;Now I can set an alert if this number gets to high and to look for pasterns &lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2013 14:25:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Indexer-Latency/m-p/81240#M16763</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2013-04-02T14:25:25Z</dc:date>
    </item>
  </channel>
</rss>

