<?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: Splitting event to two indexes in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626272#M107598</link>
    <description>&lt;P&gt;thanks. doubling my ingest doesn't sound like a great idea. It would be cheaper to send two requests.&lt;/P&gt;</description>
    <pubDate>Fri, 06 Jan 2023 22:37:02 GMT</pubDate>
    <dc:creator>klim</dc:creator>
    <dc:date>2023-01-06T22:37:02Z</dc:date>
    <item>
      <title>How to split event to two indexes?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626255#M107593</link>
      <description>&lt;P&gt;I would like to know if it is possible to be able to inject an event to a heavy forwarder via the hec and then have it be split into two events and sent to different indexes.&lt;/P&gt;
&lt;P&gt;For example I have the original log line of:&lt;/P&gt;
&lt;P&gt;ID=1 time=”&lt;SPAN&gt;2022-12-29&lt;/SPAN&gt; 16:57:41 UTC” name=”person” address=”abc” message=”some note”.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I want the event to be split but the two new events can share similar fields. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;So index1 would be: &lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ID=1 time=”&lt;SPAN&gt;2022-12-29&lt;/SPAN&gt; 16:57:41 UTC” name=”person” address=”abc”&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;And index2 would be: &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;ID=1 time=”&lt;SPAN&gt;2022-12-29&lt;/SPAN&gt; 16:57:41 UTC” message=”some note”&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 22:32:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626255#M107593</guid>
      <dc:creator>klim</dc:creator>
      <dc:date>2023-01-06T22:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splitting event to two indexes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626262#M107596</link>
      <description>&lt;P&gt;I believe it can be done.&amp;nbsp; Use the CLONE_SOURCETYPE setting in transforms.conf to create a copy of the event and give it a new sourcetype.&amp;nbsp; &amp;nbsp;Then each sourcetype should be able to use REGEX and FORMAT settings to select the fields they want.&lt;/P&gt;&lt;P&gt;You'd think that the new Ingest Actions feature would be perfect for this, but it does not offer the type of changes you want to make.&lt;/P&gt;&lt;P&gt;This would be easier using Cribl (&lt;A href="http://cribl.io" target="_blank"&gt;http://cribl.io&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;Either way, duplicating the events means doubling your ingest, with corresponding effects on your license and storage.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 21:34:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626262#M107596</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-01-06T21:34:06Z</dc:date>
    </item>
    <item>
      <title>Re: Splitting event to two indexes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626272#M107598</link>
      <description>&lt;P&gt;thanks. doubling my ingest doesn't sound like a great idea. It would be cheaper to send two requests.&lt;/P&gt;</description>
      <pubDate>Fri, 06 Jan 2023 22:37:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-split-event-to-two-indexes/m-p/626272#M107598</guid>
      <dc:creator>klim</dc:creator>
      <dc:date>2023-01-06T22:37:02Z</dc:date>
    </item>
  </channel>
</rss>

