<?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: Line Merge difficulties in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535062#M89749</link>
    <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt; yes, props.conf is pushed from CM to indexers&lt;/P&gt;&lt;P&gt;The reason that the sourcetype is being set based on host name is because the sourcetype includes the environment - e.g. dev1, dev2, prod1, prod2 etc&amp;nbsp; The source file has the same path and name on all servers.&amp;nbsp; The consumers of the logs do not necessarily know which hosts make up which environment.&amp;nbsp; Therefore, by including the environment in the sourcetype, the users can find their data more easily.&lt;/P&gt;</description>
    <pubDate>Thu, 07 Jan 2021 15:29:55 GMT</pubDate>
    <dc:creator>timrich66</dc:creator>
    <dc:date>2021-01-07T15:29:55Z</dc:date>
    <item>
      <title>Line Merge difficulties</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535027#M89747</link>
      <description>&lt;P&gt;Hello helpful people,&lt;/P&gt;&lt;P&gt;I'm afraid I have an issue that is related to many questions already asked, but I have not been able to come up with a solution.&lt;/P&gt;&lt;P&gt;I have a log file that creates large events - more than 257 lines at a time.&lt;/P&gt;&lt;P&gt;To test the file, I took an extract and uploaded it manually.&amp;nbsp; Using this file, I was able to create props.conf entry as shown below and the events ingested correctly, without breaking.&lt;/P&gt;&lt;P&gt;When I applied this to our clustered environment, the breaking has returned.&lt;/P&gt;&lt;P&gt;&lt;U&gt;Events -&lt;/U&gt;&lt;/P&gt;&lt;DIV class="raw-event normal  wrap "&gt;++++ &lt;SPAN class="t"&gt;information&lt;/SPAN&gt; &lt;SPAN class="t"&gt;2021-01-06&lt;/SPAN&gt; &lt;SPAN class="t"&gt;16:38:53&lt;/SPAN&gt; &lt;SPAN class="t"&gt;host&lt;/SPAN&gt; &lt;SPAN class="t"&gt;=&lt;/SPAN&gt;&amp;nbsp;xxxx.xxxx&lt;SPAN class="t"&gt;.net&lt;/SPAN&gt; &lt;SPAN class="t"&gt;process&lt;/SPAN&gt; &lt;SPAN class="t"&gt;=&lt;/SPAN&gt; &lt;SPAN class="t"&gt;00002fa8&lt;/SPAN&gt; &lt;SPAN class="t"&gt;thread&lt;/SPAN&gt; &lt;SPAN class="t"&gt;=&lt;/SPAN&gt; &lt;SPAN class="t"&gt;73ffe380&lt;/SPAN&gt; &lt;SPAN class="t"&gt;context&lt;/SPAN&gt; &lt;SPAN class="t"&gt;=&lt;/SPAN&gt; &lt;SPAN class="t"&gt;Server::calculate&lt;/SPAN&gt;(), &lt;SPAN class="t"&gt;module&lt;/SPAN&gt; &lt;SPAN class="t"&gt;Request&lt;/SPAN&gt; &lt;SPAN class="t"&gt;failed&lt;/SPAN&gt; &lt;SPAN class="t"&gt;with&lt;/SPAN&gt; &lt;SPAN class="t"&gt;error&lt;/SPAN&gt;(&lt;SPAN class="t"&gt;s&lt;/SPAN&gt;)&lt;SPAN class="t"&gt;:&lt;/SPAN&gt; &amp;lt;?&lt;SPAN class="t"&gt;xml&lt;/SPAN&gt; &lt;SPAN class="t"&gt;version=&lt;/SPAN&gt;'&lt;SPAN class="t"&gt;1.0&lt;/SPAN&gt;'?&amp;gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;Show all 257 lines&lt;/P&gt;&lt;DIV class="raw-event normal  wrap "&gt;[&lt;SPAN class="t"&gt;031004&lt;/SPAN&gt;] &lt;SPAN class="t"&gt;Variable&lt;/SPAN&gt; &amp;nbsp;&lt;SPAN class="t"&gt;has&lt;/SPAN&gt; &lt;SPAN class="t"&gt;no&lt;/SPAN&gt; &lt;SPAN class="t"&gt;value.&lt;/SPAN&gt; [&lt;SPAN class="t"&gt;035006&lt;/SPAN&gt;] &lt;SPAN class="t"&gt;Cannot&lt;/SPAN&gt; &lt;SPAN class="t"&gt;have&lt;/SPAN&gt; &lt;SPAN class="t"&gt;child&lt;/SPAN&gt; &amp;amp;&lt;SPAN class="t"&gt;lt&lt;/SPAN&gt;;xxxxx[&lt;SPAN class="t"&gt;E.3&lt;/SPAN&gt;] (&lt;SPAN class="t"&gt;B6I2&lt;/SPAN&gt;)&amp;amp;&lt;SPAN class="t"&gt;gt&lt;/SPAN&gt;; (xxx) &lt;SPAN class="t"&gt;on&lt;/SPAN&gt; &lt;SPAN class="t"&gt;link&lt;/SPAN&gt;&amp;nbsp;xxxxxxxxxxxxxxxxxxx&amp;nbsp;&amp;nbsp;(&lt;SPAN class="t"&gt;B6I1&lt;/SPAN&gt;)&amp;amp;&lt;SPAN class="t"&gt;gt&lt;/SPAN&gt;; &amp;lt;&lt;SPAN class="t"&gt;/clc:Error&lt;/SPAN&gt;&amp;gt; &amp;lt;&lt;SPAN class="t"&gt;/xxxx__xxxxx_xxxx_xxx_f123_2&amp;gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;Show all 257 lines&lt;/P&gt;&lt;P&gt;&lt;U&gt;props.conf&lt;/U&gt;&lt;/P&gt;&lt;P&gt;[source::///xxxx/Log/xxxxServer.log]&lt;BR /&gt;SHOULD_LINEMERGE=true&lt;BR /&gt;MAX_EVENTS=10000&lt;BR /&gt;TIME_PREFIX=\+\+\+\+ \w+&lt;/P&gt;&lt;P&gt;The reason I am using source and not sourcetype is because this source file is common to a number of environments and I am already changing sourcetype using props and transforms to determine the sourcetype per servername.&lt;/P&gt;&lt;P&gt;Thanks in advance for help - much appreciated.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 09:22:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535027#M89747</guid>
      <dc:creator>timrich66</dc:creator>
      <dc:date>2021-01-07T09:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Line Merge difficulties</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535049#M89748</link>
      <description>&lt;P&gt;How did you apply the props.conf to your cluster?&amp;nbsp; They should be installed on the indexers (pushed from the CM).&lt;/P&gt;&lt;P&gt;IMO, one should not be changing sourcetypes based on the server name.&amp;nbsp; Source types refer to a &lt;STRONG&gt;kind&lt;/STRONG&gt; of data.&amp;nbsp; Kinds do not change because the server name changed.&amp;nbsp; If you need to distinguish originating servers then use the &lt;FONT face="courier new,courier"&gt;host&lt;/FONT&gt; field.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 14:06:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535049#M89748</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-01-07T14:06:14Z</dc:date>
    </item>
    <item>
      <title>Re: Line Merge difficulties</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535062#M89749</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/213957"&gt;@richgalloway&lt;/a&gt; yes, props.conf is pushed from CM to indexers&lt;/P&gt;&lt;P&gt;The reason that the sourcetype is being set based on host name is because the sourcetype includes the environment - e.g. dev1, dev2, prod1, prod2 etc&amp;nbsp; The source file has the same path and name on all servers.&amp;nbsp; The consumers of the logs do not necessarily know which hosts make up which environment.&amp;nbsp; Therefore, by including the environment in the sourcetype, the users can find their data more easily.&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jan 2021 15:29:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/535062#M89749</guid>
      <dc:creator>timrich66</dc:creator>
      <dc:date>2021-01-07T15:29:55Z</dc:date>
    </item>
    <item>
      <title>Line Merge difficulties</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/536011#M89874</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;FYI - I have found the issue.&amp;nbsp; Deliberate mistake?&amp;nbsp; Maybe not, but it should have been obvious..&lt;/P&gt;&lt;P&gt;Original props.conf -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[source::///xxxx/Log/xxxxServer.log]&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;SHOULD_LINEMERGE=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;MAX_EVENTS=10000&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;TIME_PREFIX=\+\+\+\+ \w+&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Working props.conf&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;[source::///xxxx/Log/xxxxServer.log]&lt;BR /&gt;SHOULD_LINEMERGE = true&lt;BR /&gt;MAX_EVENTS = 10000&lt;BR /&gt;TIME_PREFIX = \+\+\+\+ \w+&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Yes, it was pesky spaces &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; Watch out for them!&amp;nbsp; All now working as planned.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jan 2021 14:35:39 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Line-Merge-difficulties/m-p/536011#M89874</guid>
      <dc:creator>timrich66</dc:creator>
      <dc:date>2021-01-15T14:35:39Z</dc:date>
    </item>
  </channel>
</rss>

