<?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 How do I troubleshoot linebreak / linemerge issues? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57196#M11160</link>
    <description>&lt;P&gt;I'm having a problem where multiple events are getting combined into a single event and I haven't been able to figure out how to fix it.&lt;/P&gt;

&lt;P&gt;For example, the following two events are being listed as one event by splunk:&lt;BR /&gt;
msg,server,City,recruit,0.12032890319824,code=0&amp;amp;desc=585,0,585,2013-06-06 15:45:58,10.80.74.124&lt;BR /&gt;
msg,client,Hero,train,805012,[{"mod":"Hero","cash":0,"gold":1800,"cardnumber":0,"heroid":46,"type":3,"act":"train"}],2013-06-06 15:45:58,10.80.74.124&lt;/P&gt;

&lt;P&gt;I have a splunk forwarder sending data to my main splunk indexer.  I'm using apps to specify the inputs/outputs for the forwarder.&lt;BR /&gt;
The sourcetype for the data in question is kotr_logknight&lt;/P&gt;

&lt;P&gt;On the indexer I have created a props.conf that contains:&lt;BR /&gt;
[kotr_logknight]&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;My understanding is that this should disable line merging so that my events shouldn't get combined.  However, it doesn't seem to affect the behavior at all.&lt;BR /&gt;
(I also tried putting props.conf on the forwarder and in with the app, and neither of those seemed to make any difference either)&lt;/P&gt;

&lt;P&gt;How can I track down what is happening during indexing to understand why the configuration setting doesn't seem to be doing what I expect?&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 14:03:04 GMT</pubDate>
    <dc:creator>Richard_</dc:creator>
    <dc:date>2020-09-28T14:03:04Z</dc:date>
    <item>
      <title>How do I troubleshoot linebreak / linemerge issues?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57196#M11160</link>
      <description>&lt;P&gt;I'm having a problem where multiple events are getting combined into a single event and I haven't been able to figure out how to fix it.&lt;/P&gt;

&lt;P&gt;For example, the following two events are being listed as one event by splunk:&lt;BR /&gt;
msg,server,City,recruit,0.12032890319824,code=0&amp;amp;desc=585,0,585,2013-06-06 15:45:58,10.80.74.124&lt;BR /&gt;
msg,client,Hero,train,805012,[{"mod":"Hero","cash":0,"gold":1800,"cardnumber":0,"heroid":46,"type":3,"act":"train"}],2013-06-06 15:45:58,10.80.74.124&lt;/P&gt;

&lt;P&gt;I have a splunk forwarder sending data to my main splunk indexer.  I'm using apps to specify the inputs/outputs for the forwarder.&lt;BR /&gt;
The sourcetype for the data in question is kotr_logknight&lt;/P&gt;

&lt;P&gt;On the indexer I have created a props.conf that contains:&lt;BR /&gt;
[kotr_logknight]&lt;BR /&gt;
SHOULD_LINEMERGE = false&lt;/P&gt;

&lt;P&gt;My understanding is that this should disable line merging so that my events shouldn't get combined.  However, it doesn't seem to affect the behavior at all.&lt;BR /&gt;
(I also tried putting props.conf on the forwarder and in with the app, and neither of those seemed to make any difference either)&lt;/P&gt;

&lt;P&gt;How can I track down what is happening during indexing to understand why the configuration setting doesn't seem to be doing what I expect?&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:03:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57196#M11160</guid>
      <dc:creator>Richard_</dc:creator>
      <dc:date>2020-09-28T14:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot linebreak / linemerge issues?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57197#M11161</link>
      <description>&lt;P&gt;Use a sample of data and import it into the data preview.&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Overviewofdatapreview"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Data/Overviewofdatapreview&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also the props,conf with the sourcetype definition has to be on the instance parsing the events (indexers, or heavy forwarders if any)&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2013 16:08:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57197#M11161</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2013-06-06T16:08:53Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot linebreak / linemerge issues?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57198#M11162</link>
      <description>&lt;P&gt;That was super helpful.  I've never added data that way so that I didn't know of the existance of the data previewer.&lt;/P&gt;

&lt;P&gt;My problem ended up being a stupid mistake.  I was changing prop.conf on the wrong machine.  I thought I was on the indexer, but I wasn't.&lt;/P&gt;

&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jun 2013 17:38:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57198#M11162</guid>
      <dc:creator>Richard_</dc:creator>
      <dc:date>2013-06-06T17:38:34Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot linebreak / linemerge issues?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57199#M11163</link>
      <description>&lt;P&gt;The GUI for this gives you a partially interactive way to test things.  Being able to immediately see results as you change things was very useful.&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2015 13:20:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57199#M11163</guid>
      <dc:creator>Richfez</dc:creator>
      <dc:date>2015-08-01T13:20:58Z</dc:date>
    </item>
    <item>
      <title>Re: How do I troubleshoot linebreak / linemerge issues?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57200#M11164</link>
      <description>&lt;P&gt;You're correct about making changes in the props.conf on the indexer. But you will need to write a regular expression to successfully break those lines so Splunk will see them as a new event&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;^msg\,\w+&lt;/CODE&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 01 Aug 2015 13:27:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-do-I-troubleshoot-linebreak-linemerge-issues/m-p/57200#M11164</guid>
      <dc:creator>skoelpin</dc:creator>
      <dc:date>2015-08-01T13:27:23Z</dc:date>
    </item>
  </channel>
</rss>

