<?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 Can you help us fix a forwarding delay occurring between event time and indexed time? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Can-you-help-us-fix-a-forwarding-delay-occurring-between-event/m-p/393388#M70244</link>
    <description>&lt;P&gt;We have set up a Splunk forwarder to forward the latest logs in the same server, but we are having an issue where there is a huge difference between indexed time and the event time. I can see the delay of almost 17 hours when I use this query to find the indexed time, event time and the delay:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=myindex sourcetype=mysourcetype host=myhost | eval delay=(_indextime-_time)/60/60 | eval indexed_time=strftime(_indextime, "%+") | table indexed_time, _time, delay
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is what i got from splunkd.log&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;01-08-2019 11:17:31.607 +0700 INFO  TailReader -   ...continuing.
01-08-2019 11:17:33.515 +0700 INFO  TcpOutputProc - Connected to idx=*heavy_forwarder*, pset=0, reuse=1.
01-08-2019 11:17:46.608 +0700 INFO  TailReader - Could not send data to output queue (structuredParsingQueue), retrying...
01-08-2019 11:17:51.609 +0700 INFO  TailReader -   ...continuing.
01-08-2019 11:17:55.286 +0700 INFO  HttpPubSubConnection - Running phone uri=/services/broker/phonehome/connection_*sourcehostip*_*sourcehostname*_*sourcehostmac*
01-08-2019 11:18:06.610 +0700 INFO  TailReader - Could not send data to output queue (structuredParsingQueue), retrying...
01-08-2019 11:18:11.610 +0700 INFO  TailReader -   ...continuing.
01-08-2019 11:18:16.611 +0700 INFO  TailReader - Could not send data to output queue (structuredParsingQueue), retrying...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This issue only occurred on this particular host. Hence, I created a limits.conf file to change the thruput limit as suggested here: &lt;/P&gt;

&lt;P&gt;link:&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Troubleshooting/Troubleshootingeventsindexingdelay"&gt;troubleshootingindexdelay&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Unfortunately, that did not resolve the issue as we still get messages in splunkd.log. &lt;/P&gt;

&lt;P&gt;Any idea which part should I look into next?&lt;/P&gt;</description>
    <pubDate>Tue, 08 Jan 2019 06:54:45 GMT</pubDate>
    <dc:creator>Nik_Shafiq</dc:creator>
    <dc:date>2019-01-08T06:54:45Z</dc:date>
    <item>
      <title>Can you help us fix a forwarding delay occurring between event time and indexed time?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-you-help-us-fix-a-forwarding-delay-occurring-between-event/m-p/393388#M70244</link>
      <description>&lt;P&gt;We have set up a Splunk forwarder to forward the latest logs in the same server, but we are having an issue where there is a huge difference between indexed time and the event time. I can see the delay of almost 17 hours when I use this query to find the indexed time, event time and the delay:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=myindex sourcetype=mysourcetype host=myhost | eval delay=(_indextime-_time)/60/60 | eval indexed_time=strftime(_indextime, "%+") | table indexed_time, _time, delay
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This is what i got from splunkd.log&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;01-08-2019 11:17:31.607 +0700 INFO  TailReader -   ...continuing.
01-08-2019 11:17:33.515 +0700 INFO  TcpOutputProc - Connected to idx=*heavy_forwarder*, pset=0, reuse=1.
01-08-2019 11:17:46.608 +0700 INFO  TailReader - Could not send data to output queue (structuredParsingQueue), retrying...
01-08-2019 11:17:51.609 +0700 INFO  TailReader -   ...continuing.
01-08-2019 11:17:55.286 +0700 INFO  HttpPubSubConnection - Running phone uri=/services/broker/phonehome/connection_*sourcehostip*_*sourcehostname*_*sourcehostmac*
01-08-2019 11:18:06.610 +0700 INFO  TailReader - Could not send data to output queue (structuredParsingQueue), retrying...
01-08-2019 11:18:11.610 +0700 INFO  TailReader -   ...continuing.
01-08-2019 11:18:16.611 +0700 INFO  TailReader - Could not send data to output queue (structuredParsingQueue), retrying...
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This issue only occurred on this particular host. Hence, I created a limits.conf file to change the thruput limit as suggested here: &lt;/P&gt;

&lt;P&gt;link:&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Troubleshooting/Troubleshootingeventsindexingdelay"&gt;troubleshootingindexdelay&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Unfortunately, that did not resolve the issue as we still get messages in splunkd.log. &lt;/P&gt;

&lt;P&gt;Any idea which part should I look into next?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 06:54:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-you-help-us-fix-a-forwarding-delay-occurring-between-event/m-p/393388#M70244</guid>
      <dc:creator>Nik_Shafiq</dc:creator>
      <dc:date>2019-01-08T06:54:45Z</dc:date>
    </item>
    <item>
      <title>Re: Can you help us fix a forwarding delay occurring between event time and indexed time?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Can-you-help-us-fix-a-forwarding-delay-occurring-between-event/m-p/393389#M70245</link>
      <description>&lt;P&gt;Looks like the queues are getting full and hence blocked. Are you sending the data/logs for this sourcetype only to one indexer? Look at the metrics.log for the pipeline issue and address them. Also, look at your props/transforms for regex improvements.&lt;/P&gt;

&lt;P&gt;You may also need to review the &lt;BR /&gt;
&lt;A href="https://wiki.splunk.com/Community:HowIndexingWorks"&gt;https://wiki.splunk.com/Community:HowIndexingWorks&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Tue, 08 Jan 2019 13:53:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Can-you-help-us-fix-a-forwarding-delay-occurring-between-event/m-p/393389#M70245</guid>
      <dc:creator>lakshman239</dc:creator>
      <dc:date>2019-01-08T13:53:28Z</dc:date>
    </item>
  </channel>
</rss>

