<?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 Splunk index in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583526#M203209</link>
    <description>&lt;P&gt;How can i populate data from primary index to summary index using collect command.&amp;nbsp;&lt;/P&gt;&lt;P&gt;By using collect command can we populate the logs from primary to summary index&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 03 Feb 2022 10:58:36 GMT</pubDate>
    <dc:creator>kajalchopade071</dc:creator>
    <dc:date>2022-02-03T10:58:36Z</dc:date>
    <item>
      <title>Splunk index</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583526#M203209</link>
      <description>&lt;P&gt;How can i populate data from primary index to summary index using collect command.&amp;nbsp;&lt;/P&gt;&lt;P&gt;By using collect command can we populate the logs from primary to summary index&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 10:58:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583526#M203209</guid>
      <dc:creator>kajalchopade071</dc:creator>
      <dc:date>2022-02-03T10:58:36Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk index</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583528#M203210</link>
      <description>&lt;P&gt;Or you can create a report, and use it for summary indexing. Normally, you might put this on a schedule e.g. hourly, but you should make sure that each report does not produce overlapping events with those events already covered by the summary index.&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 11:17:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583528#M203210</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2022-02-03T11:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk index</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583533#M203214</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241306"&gt;@kajalchopade071&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;usually summary indexes are used in three cases:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;to summarize events in a different index, in other words, you save in the summary index the results of a grouping command (e.g. stats or timechart) so, you have the already calculated values,&lt;/LI&gt;&lt;LI&gt;to save only some fields and have quicker results in search because the field extarction are already present in the summary index events,&lt;/LI&gt;&lt;LI&gt;To save some values of events for a period longer than retention.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In other words: usually in summary indexes you don't store the full events but only elaborated results of a query.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Thu, 03 Feb 2022 11:52:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-index/m-p/583533#M203214</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2022-02-03T11:52:30Z</dc:date>
    </item>
  </channel>
</rss>

