<?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: timestamp and line breaks in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354369#M64803</link>
    <description>&lt;P&gt;Is there a line breaker in the source events at all? From your post there is, so standard line breaking (using CRLF) should work. If it doesn't, there is no line feed in the source.&lt;BR /&gt;
You can try &lt;CODE&gt;BREAK_ONLY_BEFORE=DATATYPE::&lt;/CODE&gt;&lt;BR /&gt;
Unless you are dealing with multi-line events, set &lt;CODE&gt;SHOULD_LINEMERGE=false&lt;/CODE&gt;&lt;BR /&gt;
Line 7 in your props.conf above is not a valid setting, it should be &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD=128&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Also, you configured that where parsing occurs (indexer, heavy forwarder), correct?&lt;/P&gt;</description>
    <pubDate>Fri, 22 Sep 2017 00:08:53 GMT</pubDate>
    <dc:creator>s2_splunk</dc:creator>
    <dc:date>2017-09-22T00:08:53Z</dc:date>
    <item>
      <title>timestamp and line breaks</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354368#M64802</link>
      <description>&lt;P&gt;The timestamp and linebreaking doesn't seem to be working as expected. They are nagios/pnp4nagios logs.&lt;BR /&gt;
I get a burst of events similar to the below data every few seconds/minutes and it seems the first line of each data burst is being recognized for the TIMET timestamp but all other events within that data burst aren't being handled correctly. &lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;TIMET::1506034709&lt;/STRONG&gt; = timestamp in epoch time&lt;BR /&gt;
&lt;STRONG&gt;DATATYPE::&lt;/STRONG&gt; = start/end of event&lt;/P&gt;

&lt;P&gt;Data is sent in this format: &lt;STRONG&gt;DATATYPE::SERVICEPERFDATA\tTIMET::$TIMET$\tHOSTNAME::$HOSTNAME$\t&lt;/STRONG&gt;&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;Here's the data:&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;DATATYPE::HOSTPERFDATA  TIMET::1506034709   HOSTNAME::host1 HOSTPERFDATA::time=0.000342s;;;0.000000;20.000000   HOSTCHECKCOMMAND::check_tcp!255.255.25.25!443   HOSTSTATE::UP   HOSTSTATETYPE::HARD HOSTOUTPUT::TCP OK - 0.000 second response time on 255.255.25.25 port 443   
DATATYPE::HOSTPERFDATA  TIMET::1506034713   HOSTNAME::host2 HOSTPERFDATA::time=0.000368s;;;0.000000;20.000000   HOSTCHECKCOMMAND::check_tcp!255.255.25.256!443  HOSTSTATE::UP   HOSTSTATETYPE::HARD HOSTOUTPUT::TCP OK - 0.000 second response time on 255.255.25.256 port 443
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;&lt;STRONG&gt;Here's the sourcetype config: - timestamp/linebreak&lt;/STRONG&gt;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[nagios:core:perfdata]
event_breaks: (I've tried auto and every line)
BREAK_ONLY_BEFORE = ([\r\n]+)DATATYPE
SHOULD_LINEMERGE = true
TIME_FORMAT =  %s
TIME_PREFIX = TIMET::
lookahead 128
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 Sep 2017 23:34:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354368#M64802</guid>
      <dc:creator>rewritex</dc:creator>
      <dc:date>2017-09-21T23:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp and line breaks</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354369#M64803</link>
      <description>&lt;P&gt;Is there a line breaker in the source events at all? From your post there is, so standard line breaking (using CRLF) should work. If it doesn't, there is no line feed in the source.&lt;BR /&gt;
You can try &lt;CODE&gt;BREAK_ONLY_BEFORE=DATATYPE::&lt;/CODE&gt;&lt;BR /&gt;
Unless you are dealing with multi-line events, set &lt;CODE&gt;SHOULD_LINEMERGE=false&lt;/CODE&gt;&lt;BR /&gt;
Line 7 in your props.conf above is not a valid setting, it should be &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD=128&lt;/CODE&gt;.&lt;/P&gt;

&lt;P&gt;Also, you configured that where parsing occurs (indexer, heavy forwarder), correct?&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2017 00:08:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354369#M64803</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2017-09-22T00:08:53Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp and line breaks</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354370#M64804</link>
      <description>&lt;P&gt;I had to modify the props.conf on the cluster/indexers and that seemed to get it working. I was in the SH mucking around with the props.conf&lt;BR /&gt;
Thanks for the reminder.&lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME$/etc/master-apps/_cluster/local/props.conf&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;BREAK_ONLY_BEFORE=DATATYPE::
SHOULD_LINEMERGE = false
TIME_FORMAT = %s
TIME_PREFIX = TIMET::
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Tue, 29 Sep 2020 15:54:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354370#M64804</guid>
      <dc:creator>rewritex</dc:creator>
      <dc:date>2020-09-29T15:54:36Z</dc:date>
    </item>
    <item>
      <title>Re: timestamp and line breaks</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354371#M64805</link>
      <description>&lt;P&gt;Ha, he/she who's never done that, speak up now or be silent forever! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt; &lt;BR /&gt;
Glad you got it working.&lt;/P&gt;</description>
      <pubDate>Fri, 22 Sep 2017 01:49:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/timestamp-and-line-breaks/m-p/354371#M64805</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2017-09-22T01:49:01Z</dc:date>
    </item>
  </channel>
</rss>

