<?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: Issue filtering events with regex and props.conf in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/638268#M109013</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/255376"&gt;@xwill13&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;These are the props settings that I would use for your input:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ log_file_test]
MAX_TIMESTAMP_LOOKAHEAD=0
TIME_PREFIX=^
SHOULD_LINEMERGE=false
LINE_BREAKER=(\*{78}[\r\n]+)[a-zA-Z]+\s\d+/\d+/\d+
TRUNCATE=500
NO_BINARY_CHECK=true&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is usually better to play with the LINE_BREAKER and&amp;nbsp;SHOULD_LINEMERGE=false to prevent Splunk from breaking events into single lines (using the default line breaker) and then consume resources doing the merging operations.&lt;/P&gt;&lt;P&gt;Others settings are specified for improved indexing/parsing performance; TIME_FORMAT was left to let Splunk automatically interpret the timestamp with the hours and minutes part of the timestamp in the other line&lt;/P&gt;&lt;P&gt;Hope this will help you, have a good day,&lt;/P&gt;&lt;P&gt;Fabrizio&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 02 Apr 2023 20:47:34 GMT</pubDate>
    <dc:creator>LRF</dc:creator>
    <dc:date>2023-04-02T20:47:34Z</dc:date>
    <item>
      <title>Issue filtering events with regex and props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/636961#M108941</link>
      <description>&lt;P&gt;Hello, I am trying to figure out how to edit props.conf so that it splits my events properly. The events are added to a log file, which looks like this:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;Mon 01/02/2023&lt;BR /&gt;09:00 AM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;The command completed successfully.&lt;BR /&gt;&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;\\share\folder\folder\folder\file&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;Tue 01/03/2023&lt;BR /&gt;09:00 AM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;The command completed successfully.&lt;BR /&gt;&lt;BR /&gt;The system cannot find the file specified.&lt;BR /&gt;\\share\folder\folder\folder\file&lt;BR /&gt;0 file(s) copied.&lt;BR /&gt;The system cannot find the file specified.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;Wed 01/04/2023&lt;BR /&gt;09:00 AM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;The command completed successfully.&lt;BR /&gt;&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;\\share\folder\folder\folder\file&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;Thu 01/05/2023&lt;BR /&gt;09:00 AM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;The command completed successfully.&lt;BR /&gt;&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;\\share\folder\folder\folder\file&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I would like my events to look like this:&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;Mon 01/02/2023&lt;BR /&gt;09:00 AM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;The command completed successfully.&lt;BR /&gt;&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;\\share\folder\folder\folder\file&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;1 file(s) copied.&lt;/PRE&gt;&lt;P&gt;It seems like no matter what I try, I can't get splunk to separate it properly.&lt;/P&gt;&lt;P&gt;The file updates daily and I have been testing my settings by uploading a copy of the text file directly and then adding then configuring splunk to monitor the file for continuous updates.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Typically the preview for the uploaded file looks somewhat acceptable like this:&lt;/P&gt;&lt;PRE&gt;Mon 01/02/2023&lt;BR /&gt;09:00 AM&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;******************************************************************************&lt;BR /&gt;&lt;BR /&gt;The command completed successfully.&lt;BR /&gt;&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;\\share\folder\folder\folder\file&lt;BR /&gt;1 file(s) copied.&lt;BR /&gt;1 file(s) copied.&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This output would work, however I did notice that it is consistently cutting off the first line of text. The real problem comes in with the monitoring process.&lt;/P&gt;&lt;P&gt;It tends to split the data in a way that seems almost random, and definitely isn't matching my regex settings.&lt;/P&gt;&lt;P&gt;The date, the asterisks and the text get placed into separate events for reasons i dont understand.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My props.conf settings are displayed below:&lt;/P&gt;&lt;PRE&gt;[log_file_test]&lt;BR /&gt;&lt;BR /&gt;BREAK_ONLY_BEFORE = \*{78}\s*[a-zA-z]{3}\s\d{2}\/\d{2}\/\d{2}\/\d{4}&lt;BR /&gt;&lt;BR /&gt;NO_BINARY_CHECK = 1&lt;BR /&gt;&lt;BR /&gt;SHOULD_LINEMERGE=1&lt;BR /&gt;&lt;BR /&gt;category=custom&lt;BR /&gt;&lt;BR /&gt;pulldown_type=1&lt;BR /&gt;&lt;BR /&gt;disabled=false&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/PRE&gt;&lt;P&gt;Any clues as to what I might be doing wrong or neglecting?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 31 Mar 2023 19:07:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/636961#M108941</guid>
      <dc:creator>xwill13</dc:creator>
      <dc:date>2023-03-31T19:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: Issue filtering events with regex and props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/638268#M109013</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/255376"&gt;@xwill13&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;These are the props settings that I would use for your input:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ log_file_test]
MAX_TIMESTAMP_LOOKAHEAD=0
TIME_PREFIX=^
SHOULD_LINEMERGE=false
LINE_BREAKER=(\*{78}[\r\n]+)[a-zA-Z]+\s\d+/\d+/\d+
TRUNCATE=500
NO_BINARY_CHECK=true&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It is usually better to play with the LINE_BREAKER and&amp;nbsp;SHOULD_LINEMERGE=false to prevent Splunk from breaking events into single lines (using the default line breaker) and then consume resources doing the merging operations.&lt;/P&gt;&lt;P&gt;Others settings are specified for improved indexing/parsing performance; TIME_FORMAT was left to let Splunk automatically interpret the timestamp with the hours and minutes part of the timestamp in the other line&lt;/P&gt;&lt;P&gt;Hope this will help you, have a good day,&lt;/P&gt;&lt;P&gt;Fabrizio&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 02 Apr 2023 20:47:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/638268#M109013</guid>
      <dc:creator>LRF</dc:creator>
      <dc:date>2023-04-02T20:47:34Z</dc:date>
    </item>
    <item>
      <title>Re: Issue filtering events with regex and props.conf</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/638389#M109019</link>
      <description>&lt;P&gt;Thanks! This seems to have worked perfectly so far.&lt;/P&gt;</description>
      <pubDate>Mon, 03 Apr 2023 14:10:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Issue-filtering-events-with-regex-and-props-conf/m-p/638389#M109019</guid>
      <dc:creator>xwill13</dc:creator>
      <dc:date>2023-04-03T14:10:24Z</dc:date>
    </item>
  </channel>
</rss>

