<?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: Modify Splunk_TA_infoblox to separate events into indexes in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Modify-Splunk-TA-infoblox-to-separate-events-into-indexes/m-p/496166#M84640</link>
    <description>&lt;P&gt;My mistake...!&lt;/P&gt;

&lt;P&gt;The indexing process is a pipeline. There is no loop - so the "TRANSFORMS-0_branch_index" instances did not work after the infoblox:dhcp/:dns/:threatprotect was already set.&lt;/P&gt;

&lt;P&gt;So branching off in indexes has to be done as a transform for the [infoblox:file] sourcetype.&lt;/P&gt;

&lt;P&gt;Problem solved.&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 02:27:26 GMT</pubDate>
    <dc:creator>ww9rivers</dc:creator>
    <dc:date>2020-09-30T02:27:26Z</dc:date>
    <item>
      <title>Modify Splunk_TA_infoblox to separate events into indexes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Modify-Splunk-TA-infoblox-to-separate-events-into-indexes/m-p/496165#M84639</link>
      <description>&lt;P&gt;Splunk_TA_infoblox reset "sourcetype" of input events, in my case from "infoblox:file", to 3 different values -- infoblox:dns / :dhcp / :threatprotect.&lt;/P&gt;

&lt;P&gt;I am trying to modify the TA to put those events into 2 different indexes: DHCP events to "ipam", others to "ipam-secure".&lt;/P&gt;

&lt;P&gt;However I have not been able to do that. Here is what I have modified:&lt;/P&gt;

&lt;P&gt;In props.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[infoblox:dhcp]
TRANSFORMS-0_branch_index = infoblox_branch_index_ipam
. . . . . .
[infoblox:dns]
TRANSFORMS-0_branch_index = infoblox_branch_index_ipam_secure
. . . . . .
[infoblox:threatprotect]
TRANSFORMS-0_branch_index = infoblox_branch_index_ipam_secure
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;In transforms.conf:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[infoblox_branch_index_ipam]
REGEX = .*
DEST_KEY = _MetaData:Index
FORMAT = ipam

[infoblox_branch_index_ipam_secure]
REGEX = .*
DEST_KEY = _MetaData:Index
FORMAT = ipam-secure
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The idea is basically, after an input event has its sourcetype reset as the TA already does, reset its index.&lt;/P&gt;

&lt;P&gt;There are two TRANSFORMS for each raw event -- Should that work?&lt;/P&gt;

&lt;P&gt;Should I have done it differently: adding more transform items in TRANSFORMS-0_branch_source_type for the [infoblox:file] sourcetype?&lt;/P&gt;

&lt;P&gt;Any help is much appreciated! I'm running Splunk 7.0.3.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:27:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Modify-Splunk-TA-infoblox-to-separate-events-into-indexes/m-p/496165#M84639</guid>
      <dc:creator>ww9rivers</dc:creator>
      <dc:date>2020-09-30T02:27:10Z</dc:date>
    </item>
    <item>
      <title>Re: Modify Splunk_TA_infoblox to separate events into indexes</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Modify-Splunk-TA-infoblox-to-separate-events-into-indexes/m-p/496166#M84640</link>
      <description>&lt;P&gt;My mistake...!&lt;/P&gt;

&lt;P&gt;The indexing process is a pipeline. There is no loop - so the "TRANSFORMS-0_branch_index" instances did not work after the infoblox:dhcp/:dns/:threatprotect was already set.&lt;/P&gt;

&lt;P&gt;So branching off in indexes has to be done as a transform for the [infoblox:file] sourcetype.&lt;/P&gt;

&lt;P&gt;Problem solved.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 02:27:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Modify-Splunk-TA-infoblox-to-separate-events-into-indexes/m-p/496166#M84640</guid>
      <dc:creator>ww9rivers</dc:creator>
      <dc:date>2020-09-30T02:27:26Z</dc:date>
    </item>
  </channel>
</rss>

