<?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: Routing problem with props and transforms in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306787#M57844</link>
    <description>&lt;P&gt;Hi Woodcock,&lt;BR /&gt;
I want all the logs to be send to existing indexes and only few to be send to new index.&lt;BR /&gt;
Looking at this it might impact the existing indexes as well.&lt;/P&gt;</description>
    <pubDate>Fri, 31 Mar 2017 14:10:57 GMT</pubDate>
    <dc:creator>chintan_shah</dc:creator>
    <dc:date>2017-03-31T14:10:57Z</dc:date>
    <item>
      <title>Routing problem with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306785#M57842</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I am having trouble for routing the logs to separate index using props and transforms.&lt;BR /&gt;
With the below code on Splunk instance, all the logs are being send to guilogins index and not on earlier index. &lt;BR /&gt;
Also all the logs on guilogins doesnt match with the REGEX.&lt;BR /&gt;
Can any one please help me out?&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
TRANSFORMS-SET=allroute,loginroute&lt;/P&gt;

&lt;P&gt;Transforms.conf&lt;BR /&gt;
[allroute]&lt;BR /&gt;
REGEX = .*&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = indexQueue&lt;/P&gt;

&lt;P&gt;[loginroute]&lt;BR /&gt;
REGEX = .[GUI User Logged out|GUI New User Logged In].*&lt;BR /&gt;
DEST_KEY = _MetaData:Index&lt;BR /&gt;
FORMAT = guilogins&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 21:30:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306785#M57842</guid>
      <dc:creator>chintan_shah</dc:creator>
      <dc:date>2017-03-30T21:30:46Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306786#M57843</link>
      <description>&lt;P&gt;Use this instead:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;TRANSFORMS-SET=loginroute
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;And deploy to your Indexers and restart splunk instances there and check newly arriving events only (not old ones).&lt;/P&gt;</description>
      <pubDate>Thu, 30 Mar 2017 21:54:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306786#M57843</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2017-03-30T21:54:30Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306787#M57844</link>
      <description>&lt;P&gt;Hi Woodcock,&lt;BR /&gt;
I want all the logs to be send to existing indexes and only few to be send to new index.&lt;BR /&gt;
Looking at this it might impact the existing indexes as well.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 14:10:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306787#M57844</guid>
      <dc:creator>chintan_shah</dc:creator>
      <dc:date>2017-03-31T14:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306788#M57845</link>
      <description>&lt;P&gt;Hi there, I believe you should change the regular expresion on the loginroute stanza, if I'm not mistaken that regex matches more than you want.&lt;/P&gt;

&lt;P&gt;Try this &lt;CODE&gt;(GUI\sUser\sLogged\sout|GUI\sNew\sUser\sLogged\sIn)&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 14:22:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306788#M57845</guid>
      <dc:creator>alemarzu</dc:creator>
      <dc:date>2017-03-31T14:22:54Z</dc:date>
    </item>
    <item>
      <title>Re: Routing problem with props and transforms</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306789#M57846</link>
      <description>&lt;P&gt;Hi Woodcock,&lt;/P&gt;

&lt;P&gt;I have updated the regex which was creating the issue and use your suggestion of  TRANSFORMS-SET and it worked fine.&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2017 19:05:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Routing-problem-with-props-and-transforms/m-p/306789#M57846</guid>
      <dc:creator>chintan_shah</dc:creator>
      <dc:date>2017-03-31T19:05:40Z</dc:date>
    </item>
  </channel>
</rss>

