<?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: Firewall Indexing Latency in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130289#M26792</link>
    <description>&lt;P&gt;Martin thanks for your help,&lt;/P&gt;

&lt;P&gt;Scanned vs matched&lt;/P&gt;</description>
    <pubDate>Thu, 30 Jan 2014 16:52:26 GMT</pubDate>
    <dc:creator>hartfoml</dc:creator>
    <dc:date>2014-01-30T16:52:26Z</dc:date>
    <item>
      <title>Firewall Indexing Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130287#M26790</link>
      <description>&lt;P&gt;I have my firewall sending UDP to a syslog-ng folder and Splunk is watching the file in the folder&lt;/P&gt;

&lt;P&gt;I can see a latency for the latency like this&lt;BR /&gt;
&lt;CODE&gt;| eval diff_sec=(_indextime - _time)| where diff_sec &amp;gt; 0&lt;/CODE&gt;       &lt;/P&gt;

&lt;P&gt;But when I do a real-time search on the logs the view I get is sometimes much grater than the indexing latency&lt;/P&gt;

&lt;P&gt;As I run the realtime search I see this as the events found and the events looked at &lt;STRONG&gt;"4,557 of 10,017 events matched"&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;the difference continues to grow the longer I have the realtime window open. &lt;/P&gt;

&lt;P&gt;Why can't I see all the events that have been indexed?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2014 22:09:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130287#M26790</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2014-01-29T22:09:00Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Indexing Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130288#M26791</link>
      <description>&lt;P&gt;What difference is growing, indextime vs time or scanned vs matched events?&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2014 23:26:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130288#M26791</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-01-29T23:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Indexing Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130289#M26792</link>
      <description>&lt;P&gt;Martin thanks for your help,&lt;/P&gt;

&lt;P&gt;Scanned vs matched&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 16:52:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130289#M26792</guid>
      <dc:creator>hartfoml</dc:creator>
      <dc:date>2014-01-30T16:52:26Z</dc:date>
    </item>
    <item>
      <title>Re: Firewall Indexing Latency</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130290#M26793</link>
      <description>&lt;P&gt;Doing a real-time search, the number of events scanned will increase for as long as the search is running. The number of matched events will rise and fall according to how many events actually do match within the window of your real-time search.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2014 18:55:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Firewall-Indexing-Latency/m-p/130290#M26793</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2014-01-30T18:55:08Z</dc:date>
    </item>
  </channel>
</rss>

