<?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: I am running an import script for an interval of 5 mins to collect data from all sourcetypes and put it into a summary index. in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488486#M193973</link>
    <description>&lt;P&gt;Don't really understand the question. Can you please elaborate or provide an example? &lt;/P&gt;</description>
    <pubDate>Mon, 09 Mar 2020 10:41:55 GMT</pubDate>
    <dc:creator>anmolpatel</dc:creator>
    <dc:date>2020-03-09T10:41:55Z</dc:date>
    <item>
      <title>I am running an import script for an interval of 5 mins to collect data from all sourcetypes and put it into a summary index.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488485#M193972</link>
      <description>&lt;P&gt;I have a situation where in the span of 10 mins there could be a possibility that we didn't get any data from one of the sourcetype for one interval but started getting data for next interval, by this way I am loosing data in summary index. Any suggestion would be helpful. &lt;/P&gt;

&lt;P&gt;Here's a part of my query:&lt;BR /&gt;
| metadata type=sources index=abc &lt;BR /&gt;
    | search source=random &lt;BR /&gt;
    | eval earliest=lastTime - 300&lt;BR /&gt;
    | eval latest=now()&lt;BR /&gt;
    | fields earliest latest&lt;/P&gt;

&lt;P&gt;So this random source is collecting data from all the sourcetypes.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Mar 2020 19:22:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488485#M193972</guid>
      <dc:creator>Gunjan92</dc:creator>
      <dc:date>2020-03-06T19:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: I am running an import script for an interval of 5 mins to collect data from all sourcetypes and put it into a summary index.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488486#M193973</link>
      <description>&lt;P&gt;Don't really understand the question. Can you please elaborate or provide an example? &lt;/P&gt;</description>
      <pubDate>Mon, 09 Mar 2020 10:41:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488486#M193973</guid>
      <dc:creator>anmolpatel</dc:creator>
      <dc:date>2020-03-09T10:41:55Z</dc:date>
    </item>
    <item>
      <title>Re: I am running an import script for an interval of 5 mins to collect data from all sourcetypes and put it into a summary index.</title>
      <link>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488487#M193974</link>
      <description>&lt;P&gt;This is the reason that most searches of this type run at &lt;EM&gt;least&lt;/EM&gt; 5 minutes back in time, preferably an hour or more.  There really is no way around it.  You can examine your latency with a search like this:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;|tstats max(_indextime) AS indextime WHERE index=_* OR index=* BY index sourcetype _time
| stats avg(eval(indextime - _time)) AS latency BY index sourcetype
| fieldformat latency = tostring(latency, "duration")
| sort 0 - latency
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Sun, 15 Mar 2020 21:39:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/I-am-running-an-import-script-for-an-interval-of-5-mins-to/m-p/488487#M193974</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2020-03-15T21:39:27Z</dc:date>
    </item>
  </channel>
</rss>

