<?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: props.conf precedence in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77690#M15917</link>
    <description>&lt;P&gt;Actually, I can't : not all logs received on udp:514 are juniper-sa-access. The stanza set_juniper-sa-access contains a regex to check the format.&lt;/P&gt;</description>
    <pubDate>Wed, 09 Nov 2011 09:11:36 GMT</pubDate>
    <dc:creator>afaraino</dc:creator>
    <dc:date>2011-11-09T09:11:36Z</dc:date>
    <item>
      <title>props.conf precedence</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77686#M15913</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;

&lt;P&gt;I'm having a little issue related with props.conf precedence. I want to apply a transforms stanza to set a sourcetype, then another stanza to extract the Metadata:Host field for &lt;STRONG&gt;this sourcetype&lt;/STRONG&gt;. I tried this in props.conf :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::udp:514]
TRANSFORMS-changesourcetype = set_juniper-sa-access
[juniper-sa-access]
TRANSFORMS-changehost = juniper-sa-access_host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;...but it's not working. The first transform sets the sourcetype to &lt;EM&gt;juniper-sa-access&lt;/EM&gt; but the second one never applies.&lt;/P&gt;

&lt;P&gt;If I change to that, it's working, but it's not the desired behaviour :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::udp:514]
TRANSFORMS-changesourcetype = set_juniper-sa-access
TRANSFORMS-changehost = juniper-sa-access_host
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Any clue?&lt;/P&gt;

&lt;P&gt;Is it about precedence (source &amp;gt; host &amp;gt; sourcetype)? or is it because the sourcetype is set "too late" for matching the second stanza?&lt;/P&gt;

&lt;P&gt;Best Regards,&lt;/P&gt;

&lt;P&gt;Alexandre Faraino&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 09:38:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77686#M15913</guid>
      <dc:creator>afaraino</dc:creator>
      <dc:date>2011-09-19T09:38:45Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf precedence</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77687#M15914</link>
      <description>&lt;P&gt;Found that similar topic :&lt;BR /&gt;
&lt;A href="http://splunk-base.splunk.com/answers/25512/is-my-sourcetype-override-messing-up-my-field-extraction-or-am-i"&gt;http://splunk-base.splunk.com/answers/25512/is-my-sourcetype-override-messing-up-my-field-extraction-or-am-i&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;The transforms.conf is read only once. So this is a "by design" behavior. I'll try something else.&lt;/P&gt;

&lt;P&gt;Alex&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 13:34:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77687#M15914</guid>
      <dc:creator>afaraino</dc:creator>
      <dc:date>2011-09-19T13:34:42Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf precedence</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77688#M15915</link>
      <description>&lt;P&gt;Your easiest solution is to just &lt;CODE&gt;sourcetype = juniper-sa-access&lt;/CODE&gt; in the inputs.conf where you define the &lt;CODE&gt;[udp://514]&lt;/CODE&gt; stanza. All data from that input will be marked with that sourcetype.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 14:37:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77688#M15915</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-09-19T14:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf precedence</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77689#M15916</link>
      <description>&lt;P&gt;Your easiest solution is to just &lt;CODE&gt;sourcetype = juniper-sa-access&lt;/CODE&gt; in the inputs.conf where you define the &lt;CODE&gt;[udp://514]&lt;/CODE&gt; stanza. All data from that input will be marked with that sourcetype.&lt;/P&gt;</description>
      <pubDate>Mon, 19 Sep 2011 14:37:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77689#M15916</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-09-19T14:37:40Z</dc:date>
    </item>
    <item>
      <title>Re: props.conf precedence</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77690#M15917</link>
      <description>&lt;P&gt;Actually, I can't : not all logs received on udp:514 are juniper-sa-access. The stanza set_juniper-sa-access contains a regex to check the format.&lt;/P&gt;</description>
      <pubDate>Wed, 09 Nov 2011 09:11:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/props-conf-precedence/m-p/77690#M15917</guid>
      <dc:creator>afaraino</dc:creator>
      <dc:date>2011-11-09T09:11:36Z</dc:date>
    </item>
  </channel>
</rss>

