<?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: Summary index missing random events in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273912#M190217</link>
    <description>&lt;P&gt;What you are probably missing is that the event that was not included was not present in Splunk at the time the SI-populating search ran.  Run this search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; host=iad1bf5* program=ltm request request="GET /" | eval lag=tostring((_indextime - _time), "duration")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If the lag of any event is larger than the width of your timepicker range used by your SI-populating search, then it will be missed.  This is why I generally suggest people use &lt;CODE&gt;Accelerated Data Models + tstats&lt;/CODE&gt; instead of &lt;CODE&gt;Summary Index&lt;/CODE&gt;.  It has all of the advantages but none of the weaknesses, the largest of which is mishandling (missing) of late-arriving events.&lt;/P&gt;</description>
    <pubDate>Fri, 27 May 2016 15:02:38 GMT</pubDate>
    <dc:creator>woodcock</dc:creator>
    <dc:date>2016-05-27T15:02:38Z</dc:date>
    <item>
      <title>Summary index missing random events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273910#M190215</link>
      <description>&lt;P&gt;I'm trying to set up some summary indexes, but the summary index is missing random events. The scheduled search job is running, but the data is just not in the index.&lt;/P&gt;

&lt;P&gt;For example:&lt;BR /&gt;
&lt;IMG src="http://i.imgur.com/3Lbl4kL.png" alt="missing events" /&gt;&lt;BR /&gt;
Notice that the event for 11:09 is missing. Yet when I look in the job activity, the job fired off:&lt;BR /&gt;
&lt;IMG src="http://i.imgur.com/LFtzpsN.png" alt="job activity" /&gt;&lt;BR /&gt;
Note that the job at 11:10 fills in the summary index data for 11:09. Below is from the job inspection output. The times fit right where the 11:09 event is supposed to be.&lt;BR /&gt;
&lt;IMG src="http://i.imgur.com/vff4L1W.png" alt="" /&gt;&lt;/P&gt;

&lt;P&gt;This isn't a case of the job running too long. As you can see in the job list, it completes in less than a second.&lt;BR /&gt;
The query that is running is very simple:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;host=iad1bf5* program=ltm request request="GET /" | stats dc(client_ip)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I have a copy of the job inspection output, as well as the search.log, and can provide any info needed from there.&lt;BR /&gt;
This is with Splunk 6.3.2&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2016 03:42:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273910#M190215</guid>
      <dc:creator>phemmer</dc:creator>
      <dc:date>2016-05-27T03:42:32Z</dc:date>
    </item>
    <item>
      <title>Re: Summary index missing random events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273911#M190216</link>
      <description>&lt;P&gt;Finally figured this out. We have multiple search heads, and the job was running on a random one, and not replicating the data in any way.&lt;/P&gt;

&lt;P&gt;Fixed it by configuring the search heads to forward their data to the indexers: &lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata"&gt;http://docs.splunk.com/Documentation/Splunk/latest/DistSearch/Forwardsearchheaddata&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2016 13:56:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273911#M190216</guid>
      <dc:creator>phemmer</dc:creator>
      <dc:date>2016-05-27T13:56:01Z</dc:date>
    </item>
    <item>
      <title>Re: Summary index missing random events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273912#M190217</link>
      <description>&lt;P&gt;What you are probably missing is that the event that was not included was not present in Splunk at the time the SI-populating search ran.  Run this search:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; host=iad1bf5* program=ltm request request="GET /" | eval lag=tostring((_indextime - _time), "duration")
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;If the lag of any event is larger than the width of your timepicker range used by your SI-populating search, then it will be missed.  This is why I generally suggest people use &lt;CODE&gt;Accelerated Data Models + tstats&lt;/CODE&gt; instead of &lt;CODE&gt;Summary Index&lt;/CODE&gt;.  It has all of the advantages but none of the weaknesses, the largest of which is mishandling (missing) of late-arriving events.&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2016 15:02:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273912#M190217</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-05-27T15:02:38Z</dc:date>
    </item>
    <item>
      <title>Re: Summary index missing random events</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273913#M190218</link>
      <description>&lt;P&gt;You can schedule the saved search to run 15 minutes earlier.&lt;BR /&gt;
For example, if the time is 8:30.000 AM, schedule the saved search to run from -30min to -15min.&lt;BR /&gt;
in this case, the events will not be missed out.&lt;/P&gt;</description>
      <pubDate>Fri, 14 Sep 2018 13:38:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Summary-index-missing-random-events/m-p/273913#M190218</guid>
      <dc:creator>srujan9292</dc:creator>
      <dc:date>2018-09-14T13:38:29Z</dc:date>
    </item>
  </channel>
</rss>

