<?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: Event break regex - match 19 digit number in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172455#M49411</link>
    <description>&lt;P&gt;This will not work on any event NOT containing exactly (meaning more/less) 19 digits...&lt;BR /&gt;
Always build things so you can &lt;CODE&gt;[remember what they mean|work]&lt;/CODE&gt;, two years from now &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jan 2015 20:43:55 GMT</pubDate>
    <dc:creator>MuS</dc:creator>
    <dc:date>2015-01-04T20:43:55Z</dc:date>
    <item>
      <title>Event break regex - match 19 digit number</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172452#M49408</link>
      <description>&lt;P&gt;Happy New Year everyone!&lt;/P&gt;

&lt;P&gt;Regex n00b here - I am struggling to break events for a particular source. Any help would be appreciated.&lt;/P&gt;

&lt;P&gt;The line to break events is in the following format&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;"From &amp;lt;19 digit numeric string&amp;gt;@&amp;lt;misc alpha numeric string of varying length&amp;gt; &amp;lt;timestamp&amp;gt;"
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;For example:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;From 1489304828131889971@xxx Sat Jan 03 07:02:43 2015

From 1489220782115942636@82hs Fri Jan 02 08:46:51 2015
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;I want to specify an event break in props.conf with "From &amp;lt;19 digit numeric string&amp;gt;@".&lt;/P&gt;

&lt;P&gt;Can anyone help?&lt;/P&gt;

&lt;P&gt;-dave&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jan 2015 14:51:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172452#M49408</guid>
      <dc:creator>himynamesdave</dc:creator>
      <dc:date>2015-01-04T14:51:49Z</dc:date>
    </item>
    <item>
      <title>Re: Event break regex - match 19 digit number</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172453#M49409</link>
      <description>&lt;P&gt;Hi himynamesdave,&lt;/P&gt;

&lt;P&gt;try something like this as line breaker regex :&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;From\s.+?@
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;based on the assumption I understood you correct and you want everything after the &lt;CODE&gt;@&lt;/CODE&gt; as new line &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;

&lt;P&gt;cheers, MuS&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jan 2015 18:41:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172453#M49409</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-01-04T18:41:06Z</dc:date>
    </item>
    <item>
      <title>Re: Event break regex - match 19 digit number</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172454#M49410</link>
      <description>&lt;P&gt;Since you want to break the events "From &amp;lt;19digits&amp;gt;@", here is props.conf for the same.&lt;BR /&gt;
I have used \d{19} to match the exact 19 digits as you mentioned.&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
[&amp;lt; your sourcetype OR source or host &amp;gt;]&lt;BR /&gt;
BREAK_ONLY_BEFORE=From\s+\d{19}@&lt;BR /&gt;
NO_BINARY_CHECK=1&lt;BR /&gt;
SHOULD_LINEMERGE=true&lt;/P&gt;

&lt;HR /&gt;

&lt;P&gt;please let me know if the above props.conf worked for you..&lt;BR /&gt;
regex query tried to match the correct pattern is &lt;A href="https://regex101.com/r/kD3tZ1/1" target="_blank"&gt;https://regex101.com/r/kD3tZ1/1&lt;/A&gt; &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 18:33:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172454#M49410</guid>
      <dc:creator>jayannah</dc:creator>
      <dc:date>2020-09-28T18:33:58Z</dc:date>
    </item>
    <item>
      <title>Re: Event break regex - match 19 digit number</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172455#M49411</link>
      <description>&lt;P&gt;This will not work on any event NOT containing exactly (meaning more/less) 19 digits...&lt;BR /&gt;
Always build things so you can &lt;CODE&gt;[remember what they mean|work]&lt;/CODE&gt;, two years from now &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jan 2015 20:43:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172455#M49411</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2015-01-04T20:43:55Z</dc:date>
    </item>
    <item>
      <title>Re: Event break regex - match 19 digit number</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172456#M49412</link>
      <description>&lt;P&gt;Yes, I knew it. It depends on whether strict or loose pattern matching required.  That why I said, based on 19 digit pattern as per the question. &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jan 2015 20:53:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172456#M49412</guid>
      <dc:creator>jayannah</dc:creator>
      <dc:date>2015-01-04T20:53:13Z</dc:date>
    </item>
    <item>
      <title>Re: Event break regex - match 19 digit number</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172457#M49413</link>
      <description>&lt;P&gt;For the LINE_BREAKER to work there needs to be a capture group.&lt;/P&gt;

&lt;P&gt;You should specify the following in props.conf&lt;/P&gt;

&lt;P&gt;props.conf&lt;BR /&gt;
&lt;CODE&gt;SHOULD_LINEMERGE = FALSE&lt;/CODE&gt;&lt;BR /&gt;
&lt;CODE&gt;LINE_BREAKER = ([\r\n]+)From\s\d+@&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;That will break where there is a carriage return or new line, followed by From 'space' any number of digits and an @ symbol.&lt;/P&gt;

&lt;P&gt;See how you go.&lt;/P&gt;

&lt;P&gt;(It is always preferable to delimit multi-line events with LINE_BREAKER as it has significant benefits to processing speed)&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jan 2015 20:54:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Event-break-regex-match-19-digit-number/m-p/172457#M49413</guid>
      <dc:creator>eddit0r</dc:creator>
      <dc:date>2015-01-04T20:54:49Z</dc:date>
    </item>
  </channel>
</rss>

