<?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: log file not parsing properly - multiple lines per event in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470597#M99666</link>
    <description>&lt;P&gt;Take a look at this data onboarding cheat sheet published by Aplura, it is a great guide to establish your data onboarding practices:&lt;BR /&gt;
&lt;A href="https://www.aplura.com/assets/pdf/onboarding_cheatsheet.pdf"&gt;https://www.aplura.com/assets/pdf/onboarding_cheatsheet.pdf&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 31 Dec 2019 15:31:14 GMT</pubDate>
    <dc:creator>mydog8it</dc:creator>
    <dc:date>2019-12-31T15:31:14Z</dc:date>
    <item>
      <title>log file not parsing properly - multiple lines per event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470596#M99665</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;

&lt;P&gt;I have a file monitor for a log file where I am getting indexed data with multiple lines.  Example of one event:&lt;/P&gt;

&lt;P&gt;2019-12-30 09:16:41:908: Requestor: IMM_Mobile, IsLocal: False&lt;BR /&gt;
2019-12-30 09:16:41:908: 637132942019089151: Scanned CID: BARCODE:&lt;/P&gt;

&lt;P&gt;Now i notice that it is the same time but they should still be separate events.  i have read where someone suggested SHOULD_LINEMERGE = false, however if I am reading the documentation correctly, the SHOULD_LINEMERGE = true and BREAK_ONLY_BEFORE_DATE = true being the defaults should be processing the above as two separate events.  What am I misunderstanding?&lt;/P&gt;

&lt;P&gt;I am hesitant to configure SHOULD_LINEMERGE = false because I think it may be needed for other events that span multiple lines.&lt;/P&gt;

&lt;P&gt;only other thing I can think of is possibly my props/transforms might be screwing with the data in some other way.  Below are what I think are the relevant portions of my props/transforms:&lt;/P&gt;

&lt;P&gt;Props:&lt;BR /&gt;
[mySourceType]&lt;BR /&gt;
TRANSFORMS-set= setnull,setparsing&lt;BR /&gt;
TRANSFORMS-sourcetype= setNewSourceType&lt;/P&gt;

&lt;P&gt;Transforms:&lt;BR /&gt;
[setnull]&lt;BR /&gt;
REGEX = .&lt;BR /&gt;
DEST_KEY = queue&lt;BR /&gt;
FORMAT = nullQueue&lt;/P&gt;

&lt;P&gt;[setparsing]&lt;BR /&gt;
REGEX = \b(?:offline|online|\d{4}-d{2}-d{2}\s+\d{2}:\d{2}:\d{2}:\d{3}:\s+\d{18}:\s)\b&lt;BR /&gt;
DESK_KEY = queue&lt;BR /&gt;
FORMAT = indexQueue&lt;/P&gt;

&lt;P&gt;[setNewSourceType]&lt;BR /&gt;
REGEX = \b(\d{4}-d{2}-d{2}\s+\d{2}:\d{2}:\d{2}:\d{3}:\s+\d{18}:\s)&lt;BR /&gt;
FORMAT = sourcetype::NewSourceType&lt;BR /&gt;
DEST_KEY = MetaData:Sourcetype&lt;/P&gt;

&lt;P&gt;Thanks for any assistance!&lt;BR /&gt;
David&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 03:27:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470596#M99665</guid>
      <dc:creator>dglass0215</dc:creator>
      <dc:date>2020-09-30T03:27:17Z</dc:date>
    </item>
    <item>
      <title>Re: log file not parsing properly - multiple lines per event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470597#M99666</link>
      <description>&lt;P&gt;Take a look at this data onboarding cheat sheet published by Aplura, it is a great guide to establish your data onboarding practices:&lt;BR /&gt;
&lt;A href="https://www.aplura.com/assets/pdf/onboarding_cheatsheet.pdf"&gt;https://www.aplura.com/assets/pdf/onboarding_cheatsheet.pdf&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 31 Dec 2019 15:31:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470597#M99666</guid>
      <dc:creator>mydog8it</dc:creator>
      <dc:date>2019-12-31T15:31:14Z</dc:date>
    </item>
    <item>
      <title>Re: log file not parsing properly - multiple lines per event</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470598#M99667</link>
      <description>&lt;P&gt;While this might be slightly useful it does not answer my question.  Do you know why the two lines above are one event?  And do you know how I can fix it?  Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2020 18:58:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/log-file-not-parsing-properly-multiple-lines-per-event/m-p/470598#M99667</guid>
      <dc:creator>dglass0215</dc:creator>
      <dc:date>2020-01-02T18:58:16Z</dc:date>
    </item>
  </channel>
</rss>

