<?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: use props.conf  and or transforms.conf to parse log file in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/615017#M106382</link>
    <description>&lt;P&gt;Thanks again for the clarification - I am still learning!&lt;/P&gt;</description>
    <pubDate>Wed, 28 Sep 2022 14:05:38 GMT</pubDate>
    <dc:creator>eholz1</dc:creator>
    <dc:date>2022-09-28T14:05:38Z</dc:date>
    <item>
      <title>How do I use props.conf  and or transforms.conf to parse log file?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614813#M106364</link>
      <description>&lt;P&gt;I would like to use props.conf and/or transforms.conf to parse data coming from a generic&lt;/P&gt;
&lt;P&gt;single line log file using regex to search for "Error" or "Notice" I did a test for my regex in regex 101, and the regex seems ok. regex = (?&amp;lt;=Error)(.*$)&lt;/P&gt;
&lt;P&gt;I do have a sourcetype for the incoming data - what should I be looking for and what files should I edit to&lt;/P&gt;
&lt;P&gt;allow this?&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;eholz1&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 20:53:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614813#M106364</guid>
      <dc:creator>eholz1</dc:creator>
      <dc:date>2022-09-27T20:53:27Z</dc:date>
    </item>
    <item>
      <title>Re: use props.conf  and or transforms.conf to parse log file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614819#M106365</link>
      <description>&lt;P&gt;To parse that one field at search-time (the best option, IMO), you can use an EXTRACT setting in props.conf.&amp;nbsp; No transform is needed.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[mysourcetype]
EXTRACT-error = Error(?&amp;lt;Error&amp;gt;.*)$&lt;/LI-CODE&gt;&lt;P&gt;Note the required named capture group in the regex.&amp;nbsp; Also, avoid using lookbehind in regexes as they're expensive and usually unnecessary.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 19:39:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614819#M106365</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-09-27T19:39:42Z</dc:date>
    </item>
    <item>
      <title>Re: use props.conf  and or transforms.conf to parse log file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614824#M106367</link>
      <description>&lt;P&gt;hello richgallowy,&lt;/P&gt;&lt;P&gt;I will give this a shot, and see what happens.&lt;/P&gt;&lt;P&gt;and come back if I have any questions.&amp;nbsp; could I add an "OR" to this like:&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;EXTRACT-error = Error(?&amp;lt;Error&amp;gt;.*)$&lt;/PRE&gt;&lt;P&gt;OR Notice(?&amp;lt;Notice&amp;gt;.*)$&lt;/P&gt;&lt;P&gt;thanks for the support,&lt;/P&gt;&lt;P&gt;eholz1&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 20:27:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614824#M106367</guid>
      <dc:creator>eholz1</dc:creator>
      <dc:date>2022-09-27T20:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: use props.conf  and or transforms.conf to parse log file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614830#M106368</link>
      <description>&lt;P&gt;There is nothing to stop you from doing that, but it may not do what you expect.&lt;/P&gt;&lt;P&gt;If you need to extract both Error and Notice fields then use two EXTRACT settings.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;EXTRACT-error = Error(?&amp;lt;Error&amp;gt;.*)$
EXTRACT-notice = Notice(?&amp;lt;Notice&amp;gt;.*)$&lt;/LI-CODE&gt;</description>
      <pubDate>Tue, 27 Sep 2022 21:09:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614830#M106368</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-09-27T21:09:55Z</dc:date>
    </item>
    <item>
      <title>Re: use props.conf  and or transforms.conf to parse log file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614833#M106369</link>
      <description>&lt;P&gt;Thanks again for the tips.&lt;/P&gt;&lt;P&gt;Now one last dump question - how do I verify that this works?&lt;/P&gt;&lt;P&gt;Do I need any other settings in the props.conf file to allow the data to be viewed in a search?&lt;/P&gt;&lt;P&gt;When I configure the props.conf file with the source "my_source", I still see all the data in the log file that i do not need.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks again,&lt;/P&gt;&lt;P&gt;eholz1&lt;/P&gt;</description>
      <pubDate>Tue, 27 Sep 2022 22:01:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614833#M106369</guid>
      <dc:creator>eholz1</dc:creator>
      <dc:date>2022-09-27T22:01:55Z</dc:date>
    </item>
    <item>
      <title>Re: use props.conf  and or transforms.conf to parse log file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614839#M106370</link>
      <description>&lt;P&gt;You'll know the extractions work when you see the new fields on the left side of the results or when you see values from &lt;FONT face="courier new,courier"&gt;| table Error Notice&lt;/FONT&gt;.&lt;/P&gt;&lt;P&gt;Yes, you will still see field "you do not need".&amp;nbsp; Nothing in the OP asked about getting rid of anything.&amp;nbsp; You probably don't want to get rid of anything at this points, because you may need it for another use case.&amp;nbsp; You can, however, only show what you need by using the &lt;FONT face="courier new,courier"&gt;table&lt;/FONT&gt; command as above.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2022 00:12:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/614839#M106370</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-09-28T00:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: use props.conf  and or transforms.conf to parse log file</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/615017#M106382</link>
      <description>&lt;P&gt;Thanks again for the clarification - I am still learning!&lt;/P&gt;</description>
      <pubDate>Wed, 28 Sep 2022 14:05:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-use-props-conf-and-or-transforms-conf-to-parse-log-file/m-p/615017#M106382</guid>
      <dc:creator>eholz1</dc:creator>
      <dc:date>2022-09-28T14:05:38Z</dc:date>
    </item>
  </channel>
</rss>

