<?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: Troubleshooting props.cof and transforms.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60870#M12100</link>
    <description>&lt;P&gt;Alright. I moved my extraction to SH and did a search-time extraction via props.conf. No luck.&lt;BR /&gt;
WHen I search for my source type I dont see that new field appear. I have only done debug/refresh not service restart. In addition, I've tested my regex via pcregextest command and it was successful. &lt;/P&gt;

&lt;P&gt;I need to find out which debugger to turn on, to see errors. thx&lt;/P&gt;</description>
    <pubDate>Wed, 11 Sep 2013 20:52:32 GMT</pubDate>
    <dc:creator>zislin</dc:creator>
    <dc:date>2013-09-11T20:52:32Z</dc:date>
    <item>
      <title>Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60867#M12097</link>
      <description>&lt;P&gt;I am trying to add new app to do some field extraction at index time. I've used a working app to get my folders and files created. I've tested my regex in online regex tester tools. Restarted service but no luck.&lt;/P&gt;

&lt;P&gt;Can somebody direct me to which processor I need to set to debug logging mode to troubleshoot my issue?&lt;/P&gt;

&lt;P&gt;Thanks&lt;BR /&gt;
= ==============================&lt;BR /&gt;
we have multiple servers performing different roles in splunk. So to make search heads life easier, I was thinking on doing this particular extraction on heavy forwarder.&lt;/P&gt;

&lt;P&gt;Here is the props file:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[someDevice]
MAX_TIMESTAMP_LOOKAHEAD = 15
TIME_FORMAT = %b %d %H:%M:%S
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)
TRANSFORMS-getMyFields = get_type
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Here is transforms:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[get_type]
REGEX = ]\:\s(.+?\s[\d]?[\d]?[\d]?)
FORMAT = event_type::$1
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;HR /&gt;

&lt;P&gt;My regex is a bitty cumbersome but that is due to various data coming.&lt;BR /&gt;
Sample of data is as follows:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;Sep 11 15:47:20 111.111.111.111 blabla[123]: sometype on bla bla bla the rest doesnt matter
Sep 11 15:47:20 111.111.111.111 blabla[123]: othertype at bla bla bla the rest doesnt matter
Sep 11 15:47:20 111.111.111.111 blabla[123]: newtype 11 for bla bla bla the rest doesnt matter
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I want to extract "sometype", "othertype", "newtype 11".&lt;BR /&gt;
Last one makes my extraction tricky.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 19:54:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60867#M12097</guid>
      <dc:creator>zislin</dc:creator>
      <dc:date>2013-09-11T19:54:16Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60868#M12098</link>
      <description>&lt;P&gt;No idea. However, if you post props.conf and transforms.conf stanzas here, someone will probably be able to help you.&lt;/P&gt;

&lt;P&gt;Also, I might as well be the first to ask: why an index time field extraction? A search time field extraction is just as fast, easier to create, and much more flexible.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 19:59:21 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60868#M12098</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2013-09-11T19:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60869#M12099</link>
      <description>&lt;P&gt;Like lguinn says, do it search-time on the SH instead;&lt;/P&gt;

&lt;P&gt;props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[your_sourcetype/source/host]
EXTRACT-blah = \]:\s(?&amp;lt;event_type&amp;gt;\S+(\s\d+)?)
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Should work.&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 20:35:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60869#M12099</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-11T20:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60870#M12100</link>
      <description>&lt;P&gt;Alright. I moved my extraction to SH and did a search-time extraction via props.conf. No luck.&lt;BR /&gt;
WHen I search for my source type I dont see that new field appear. I have only done debug/refresh not service restart. In addition, I've tested my regex via pcregextest command and it was successful. &lt;/P&gt;

&lt;P&gt;I need to find out which debugger to turn on, to see errors. thx&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 20:52:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60870#M12100</guid>
      <dc:creator>zislin</dc:creator>
      <dc:date>2013-09-11T20:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60871#M12101</link>
      <description>&lt;P&gt;just what does your regex look like. What you have in your original question has errors.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 21:06:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60871#M12101</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-11T21:06:19Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60872#M12102</link>
      <description>&lt;P&gt;The example I provided does indeed work. Tested on the sample events you provided.  /K&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 21:17:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60872#M12102</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-11T21:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60873#M12103</link>
      <description>&lt;P&gt;I would use the following regex, though&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[your_sourcetype/source/host]&lt;BR /&gt;
EXTRACT-blah = \]:\s(?&amp;lt;event_type&amp;gt;\S+(?:\s\d+)?)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;As I have found that sometimes Splunk is picky about capturing vs. non-capturing groups.  Or even&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;[your_sourcetype/source/host]&lt;BR /&gt;
EXTRACT-blah = \]:\s(?&amp;lt;event_type&amp;gt;.*?)\s(?:on|at|for)\s&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Sep 2013 23:51:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60873#M12103</guid>
      <dc:creator>lguinn2</dc:creator>
      <dc:date>2013-09-11T23:51:18Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60874#M12104</link>
      <description>&lt;P&gt;hi lguinn, that could be good to know, though I tested it and it did not complain on the nested, so-to-speak, capturing groups.&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2013 08:00:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60874#M12104</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-12T08:00:17Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60875#M12105</link>
      <description>&lt;P&gt;I've tested my regex with pcregextest command line tool and it was happy.&lt;/P&gt;

&lt;P&gt;My regex is&lt;BR /&gt;
 &lt;CODE&gt;]\:\s(?&amp;lt;event_type&amp;gt;.+?\s[\d]?[\d]?[\d]?)&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Does anybody know if I have to restart Splunk services when I am adding a new app via command line on search head?&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2013 13:53:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60875#M12105</guid>
      <dc:creator>zislin</dc:creator>
      <dc:date>2013-09-12T13:53:11Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60876#M12106</link>
      <description>&lt;P&gt;The answer depends greatly upon the application.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2013 13:56:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60876#M12106</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2013-09-12T13:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60877#M12107</link>
      <description>&lt;P&gt;At this point, the only thing I am trying to do, is to extract one field from data coming from one existing sourcetype. App is not visible. That's it&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2013 14:05:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60877#M12107</guid>
      <dc:creator>zislin</dc:creator>
      <dc:date>2013-09-12T14:05:07Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting props.cof and transforms.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60878#M12108</link>
      <description>&lt;P&gt;zislin,&lt;/P&gt;

&lt;P&gt;I think you should escape the initial closing square bracket. And you don't need to put your &lt;CODE&gt;\d&lt;/CODE&gt;'s in character classes (&lt;CODE&gt;[]&lt;/CODE&gt;).&lt;/P&gt;

&lt;P&gt;If this regex works in pcregextest - fine - but does it work in Splunk? I think you should test that first, before committing it to your production environment.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2013 19:02:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Troubleshooting-props-cof-and-transforms-conf/m-p/60878#M12108</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-09-12T19:02:07Z</dc:date>
    </item>
  </channel>
</rss>

