<?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 Question regarding summary index with saved search in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400507#M167908</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have created a saved search to populate summary index. I am running saved search for every 5 minutes.&lt;/P&gt;

&lt;P&gt;What i want is, first time when the saved search runs, it should run with time range as all time.&lt;BR /&gt;
And from the second time on wards, saved search should with time range as "last 5 mins" (ie, latest=now and earliest=last time when ss ran succesfully)&lt;/P&gt;

&lt;P&gt;So that i will avoid duplicate of data in summary index.&lt;/P&gt;

&lt;P&gt;How to achieve this?&lt;/P&gt;

&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
    <pubDate>Mon, 13 Aug 2018 14:36:54 GMT</pubDate>
    <dc:creator>chinmayc469</dc:creator>
    <dc:date>2018-08-13T14:36:54Z</dc:date>
    <item>
      <title>Question regarding summary index with saved search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400507#M167908</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have created a saved search to populate summary index. I am running saved search for every 5 minutes.&lt;/P&gt;

&lt;P&gt;What i want is, first time when the saved search runs, it should run with time range as all time.&lt;BR /&gt;
And from the second time on wards, saved search should with time range as "last 5 mins" (ie, latest=now and earliest=last time when ss ran succesfully)&lt;/P&gt;

&lt;P&gt;So that i will avoid duplicate of data in summary index.&lt;/P&gt;

&lt;P&gt;How to achieve this?&lt;/P&gt;

&lt;P&gt;Thanks in advance.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 14:36:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400507#M167908</guid>
      <dc:creator>chinmayc469</dc:creator>
      <dc:date>2018-08-13T14:36:54Z</dc:date>
    </item>
    <item>
      <title>Re: Question regarding summary index with saved search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400508#M167909</link>
      <description>&lt;P&gt;The first all time search, you can probably run manually, there after, you should chose earliest and latest with little bit of padding. latest=now is not a good practice as you are not accounting for the delay in the raw data. You can do something like earliest=-8m@m latest=-3m@m so that you account for 180 seconds of delay depending on how busy your indexers and forwarders are.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 15:59:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400508#M167909</guid>
      <dc:creator>pradeepkumarg</dc:creator>
      <dc:date>2018-08-13T15:59:59Z</dc:date>
    </item>
    <item>
      <title>Re: Question regarding summary index with saved search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400509#M167910</link>
      <description>&lt;P&gt;Yep, run the first saved search manually then schedule it thereafter &lt;/P&gt;</description>
      <pubDate>Mon, 13 Aug 2018 17:35:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400509#M167910</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2018-08-13T17:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: Question regarding summary index with saved search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400510#M167911</link>
      <description>&lt;P&gt;how about in production machines? we will not have access to change once it is gone to production.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 04:48:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400510#M167911</guid>
      <dc:creator>chinmayc469</dc:creator>
      <dc:date>2018-08-14T04:48:47Z</dc:date>
    </item>
    <item>
      <title>Re: Question regarding summary index with saved search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400511#M167912</link>
      <description>&lt;P&gt;I don't get what you're asking.. On your production servers, you should backfill against all-time then once your backfilled, you should set up a scheduled search which will populate your summary index going forward. I would also suggest using the python script to backfill. This gives you the ability to ignore data thats already been backfilled and you can run parallel backfills without duplicates &lt;/P&gt;

&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/7.1.2/Knowledge/Managesummaryindexgapsandoverlaps"&gt;https://docs.splunk.com/Documentation/Splunk/7.1.2/Knowledge/Managesummaryindexgapsandoverlaps&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 14 Aug 2018 13:35:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Question-regarding-summary-index-with-saved-search/m-p/400511#M167912</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2018-08-14T13:35:18Z</dc:date>
    </item>
  </channel>
</rss>

