<?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: Indexing the results of a search in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749254#M242115</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/243511"&gt;@beano501&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as also&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/225168"&gt;@ITWhisperer&lt;/a&gt;&amp;nbsp;hinted, the best solution is scheduling a search that extracts only the fields you need and storage results in a summary index using the collect command.&lt;/P&gt;&lt;P&gt;Only one attention: you cannot use a sourcetype different than "stash" because, otherwise you have to pay twice the license.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
    <pubDate>Fri, 04 Jul 2025 10:43:36 GMT</pubDate>
    <dc:creator>gcusello</dc:creator>
    <dc:date>2025-07-04T10:43:36Z</dc:date>
    <item>
      <title>Indexing the results of a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749251#M242113</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;I'm ingesting data from Azure that contains (as part of it) a syslog message, I have the vendor specific application for this syslog message format.&lt;/P&gt;&lt;P&gt;Simplified structure below.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;{
   CollectorHostName: xxxxx
   Computer: xxxxx
   EventTime: 2025-06-27T07:19:45Z
   Facility: local7
   HostIP: xx.xx.xx.xx
   SyslogMessage: logver=704072731 timestamp=1750983585 devname="xxx" devid="xxx" vd="root" date=2025-06-27 time=00:19:45 eventtime=1751008785866135964 tz="-0700" logid="0100032002" type="event" subtype="system" level="alert" ........."
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;What I would ideally like to be able to do, is extract (via a search) the "SyslogMessage" field and then re-index this into a new index (and appropriate sourcetype) so that the syslog message can be processed in "the normal way" by the vender specific application.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Does anyone know how I can achieve this? Many thanks in advance.&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 10:07:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749251#M242113</guid>
      <dc:creator>beano501</dc:creator>
      <dc:date>2025-07-04T10:07:45Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing the results of a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749252#M242114</link>
      <description>&lt;P&gt;Have you considered using a summary index to hold the extracted field(s)?&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 10:16:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749252#M242114</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2025-07-04T10:16:17Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing the results of a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749254#M242115</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/243511"&gt;@beano501&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as also&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/225168"&gt;@ITWhisperer&lt;/a&gt;&amp;nbsp;hinted, the best solution is scheduling a search that extracts only the fields you need and storage results in a summary index using the collect command.&lt;/P&gt;&lt;P&gt;Only one attention: you cannot use a sourcetype different than "stash" because, otherwise you have to pay twice the license.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 10:43:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749254#M242115</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-07-04T10:43:36Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing the results of a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749255#M242116</link>
      <description>&lt;P&gt;As&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/161352"&gt;@gcusello&lt;/a&gt;&amp;nbsp;says, with summary indexing, you have to bear in mind the licensing costs, and it partly depends on the sourcetype (stash vs non-stash), but it also depends on ingest- or workload- -based licensing model - for more details see&amp;nbsp;&lt;A href="https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/9.4/use-data-summaries-to-accelerate-searches/use-summary-indexing-for-increased-search-efficiency#ariaid-title5" target="_blank" rel="noopener"&gt;here&lt;/A&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 10:56:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749255#M242116</guid>
      <dc:creator>ITWhisperer</dc:creator>
      <dc:date>2025-07-04T10:56:44Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing the results of a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749259#M242117</link>
      <description>&lt;P&gt;Thanks for the responses, I had only really considered using "summary indexes" as part of the usual summary index commands sitimechart etc.&lt;BR /&gt;&lt;BR /&gt;What I have got working is&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;index=xxxxx sourcetype="mscs:kql"
| eval _raw = SyslogMessage
| fields _raw
| collect index=main sourcetype=fortigate_event run_in_preview=true&lt;/LI-CODE&gt;&lt;P&gt;Which achieves what I am after. I appreciate this approach would impact licensing, but it will be low volume.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 12:45:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749259#M242117</guid>
      <dc:creator>beano501</dc:creator>
      <dc:date>2025-07-04T12:45:07Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing the results of a search</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749260#M242118</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/243511"&gt;@beano501&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;good for you, see next time!&lt;/P&gt;&lt;P&gt;Ciao and happy splunking&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;P.S.: Karma Points are appreciated by all the contributors &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Jul 2025 13:09:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Indexing-the-results-of-a-search/m-p/749260#M242118</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2025-07-04T13:09:05Z</dc:date>
    </item>
  </channel>
</rss>

