<?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 LINEMERGE / props.conf issues on XML in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/LINEMERGE-props-conf-issues-on-XML/m-p/151604#M30849</link>
    <description>&lt;P&gt;Greetings,&lt;/P&gt;

&lt;P&gt;I'm receiving XML files and noticed that the first half (around 257 lines) is a single event, but everything after that is a separate event.&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://i.imgur.com/michEb2.png" alt="screenshot" title="Screenshot of results" /&gt;&lt;BR /&gt;
Reading the documentation, I see mention of modifying the props.conf to fix this. So, I've decided to use the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::elemental_job]
SHOULD_LINEMERGE = true
MAX_EVENTS = 2000
BREAK_ONLY_BEFORE = ^(&amp;lt;command)
MUST_NOT_BREAK_BEFORE = ^(&amp;lt;/command) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, this does not work. It seems to have no effect actually. &lt;/P&gt;

&lt;P&gt;Can someone tell me what I'm doing wrong?&lt;/P&gt;</description>
    <pubDate>Tue, 16 Dec 2014 14:32:36 GMT</pubDate>
    <dc:creator>helius</dc:creator>
    <dc:date>2014-12-16T14:32:36Z</dc:date>
    <item>
      <title>LINEMERGE / props.conf issues on XML</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINEMERGE-props-conf-issues-on-XML/m-p/151604#M30849</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;

&lt;P&gt;I'm receiving XML files and noticed that the first half (around 257 lines) is a single event, but everything after that is a separate event.&lt;/P&gt;

&lt;P&gt;&lt;IMG src="http://i.imgur.com/michEb2.png" alt="screenshot" title="Screenshot of results" /&gt;&lt;BR /&gt;
Reading the documentation, I see mention of modifying the props.conf to fix this. So, I've decided to use the following:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::elemental_job]
SHOULD_LINEMERGE = true
MAX_EVENTS = 2000
BREAK_ONLY_BEFORE = ^(&amp;lt;command)
MUST_NOT_BREAK_BEFORE = ^(&amp;lt;/command) 
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;However, this does not work. It seems to have no effect actually. &lt;/P&gt;

&lt;P&gt;Can someone tell me what I'm doing wrong?&lt;/P&gt;</description>
      <pubDate>Tue, 16 Dec 2014 14:32:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINEMERGE-props-conf-issues-on-XML/m-p/151604#M30849</guid>
      <dc:creator>helius</dc:creator>
      <dc:date>2014-12-16T14:32:36Z</dc:date>
    </item>
    <item>
      <title>Re: LINEMERGE / props.conf issues on XML</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/LINEMERGE-props-conf-issues-on-XML/m-p/151605#M30850</link>
      <description>&lt;P&gt;After much research, found the solution......&lt;/P&gt;

&lt;P&gt;I realized that the forwarders don't actually handle working with the data I see on the search head. This is done on the indexers. So I added the following to the props.conf on the indexers we use and it works perfectly.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[source::/opt/elemental_se/web/log/*/job_*/*_emecmd.xml]
SHOULD_LINEMERGE = true
TRUNCATE = 0
MAX_EVENTS = 5000
BREAK_ONLY_BEFORE = ^(&amp;lt;command)
MUST_NOT_BREAK_BEFORE = ^(&amp;lt;/command)
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 02 Jan 2015 17:08:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/LINEMERGE-props-conf-issues-on-XML/m-p/151605#M30850</guid>
      <dc:creator>helius</dc:creator>
      <dc:date>2015-01-02T17:08:57Z</dc:date>
    </item>
  </channel>
</rss>

