<?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: Multiple timestamps in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106630#M27745</link>
    <description>&lt;P&gt;I tried to get around this by providing a custom datetime.xml based on the suggestion from: &lt;A href="http://splunk-base.splunk.com/answers/1807/2-different-timestamps-in-single-log"&gt;http://splunk-base.splunk.com/answers/1807/2-different-timestamps-in-single-log&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It worked if I manually uploaded the log file and previewed it via splunk web. The example I provided got parsed into 4 events. But once the log files got pumped in to splunk via a forwarder, multiple events are merged into one. Any other configuartion options that I should try?&lt;/P&gt;</description>
    <pubDate>Wed, 27 Feb 2013 15:57:33 GMT</pubDate>
    <dc:creator>chiwang</dc:creator>
    <dc:date>2013-02-27T15:57:33Z</dc:date>
    <item>
      <title>Multiple timestamps</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106628#M27743</link>
      <description>&lt;P&gt;I have a log file that contains multiple formats of timestamps. Splunk, for some reasons only picks up the first one and uses it as an event boundry. Examples:&lt;/P&gt;

&lt;P&gt;Event 1) Splunk creates one event with event time &lt;STRONG&gt;&lt;EM&gt;2013-02-27 10:25:15,871&lt;/EM&gt;&lt;/STRONG&gt;.&lt;BR /&gt;
 |&lt;STRONG&gt;&lt;EM&gt;2013-02-27 10:25:15,871&lt;/EM&gt;&lt;/STRONG&gt;|[ACTIVE] ExecuteThread: '8' for queue: 'worker1'|com.testClass|INFO|userId|log xyz&lt;BR /&gt;
[gcpause][&lt;STRONG&gt;Wed Feb 27 10:25:15 2013&lt;/STRONG&gt;][00541] Thread "[ACTIVE] ExecuteThread: '3' for queue: 'worker1'" id=319 idx=0x468 tid=1851 was in object alloc 2199.796 ms from 340475.304 s&lt;BR /&gt;
[gcpause][&lt;STRONG&gt;Wed Feb 27 10:25:15 2013&lt;/STRONG&gt;][00541] Thread "[ACTIVE] ExecuteThread: '30' for queue: 'worker2'" id=13938 idx=0x69c tid=22637 was in object alloc 2197.764 ms from 340475.307 s&lt;BR /&gt;
[gcpause][&lt;STRONG&gt;Wed Feb 27 10:25:15 2013&lt;/STRONG&gt;][00541] Thread "[ACTIVE] ExecuteThread: '32' for queue: 'worker3'" id=15420 idx=0x6f0 tid=13669 was in object alloc 2191.594 ms from 340475.313 s&lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
Event 2) Splunk creates one event with event time &lt;STRONG&gt;2013-02-28 08:52:50,564&lt;/STRONG&gt;.&lt;BR /&gt;
 |&lt;STRONG&gt;&lt;EM&gt;2013-02-28 08:52:50,564&lt;/EM&gt;&lt;/STRONG&gt;|[ACTIVE] ExecuteThread: '41' for queue: 'worker1'|com.someClass|ERROR|userId|&lt;BR /&gt;
URI: [GET] /test/testURL&lt;BR /&gt;
java.lang.IllegalStateException: Response already committed&lt;BR /&gt;
         stacktrace line1&lt;BR /&gt;
         stacktrace line2&lt;BR /&gt;
&amp;lt;&lt;STRONG&gt;Feb 28, 2013 8:52:50 AM EST&lt;/STRONG&gt;&amp;gt; &lt;ERROR&gt; &lt;HTTP&gt; &lt;ERROR_CODE&gt; &amp;lt;[ServletContext@226845581[app:test module:test.war path: spec-version:2.5]] Servlet failed with Exception&lt;BR /&gt;
java.lang.IllegalStateException: Response already committed&lt;BR /&gt;
    stacktrace line1&lt;BR /&gt;
         stacktrace line2&lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
Event 3) Splunk creates one event with event time &lt;STRONG&gt;&lt;EM&gt;2013-02-27 11:14:05,333&lt;/EM&gt;&lt;/STRONG&gt;.&lt;BR /&gt;
 |&lt;STRONG&gt;&lt;EM&gt;2013-02-27 11:14:05,333&lt;/EM&gt;&lt;/STRONG&gt;|[ACTIVE] ExecuteThread: '4' for queue: 'worker'|com.testClass|INFO|userId|HttpServletRequest:&lt;BR /&gt;
      HttpServletRequest parameters:&lt;BR /&gt;
      param 1&lt;BR /&gt;
      param 2&lt;BR /&gt;
[INFO ] [&lt;STRONG&gt;20130227 11:14:07.291&lt;/STRONG&gt;] [vendorProduct] [VendorConnection] .dispatchResponses(): caught Exception during read... &lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
props.conf:&lt;BR /&gt;
[mysourcetype]&lt;BR /&gt;
TZ = 'America/New_York'&lt;BR /&gt;
NO_BINARY_CHECK = 1&lt;BR /&gt;
pulldown_type = 1&lt;BR /&gt;
REPORT-r13 = pipe_app_log_fields, source_metadata, source_region_metadata&lt;BR /&gt;
MAX_EVENTS = 10000&lt;BR /&gt;
DATETIME_CONFIG=/etc/system/local/custom_datetime.xml&lt;BR /&gt;
&lt;BR /&gt;&lt;BR /&gt;
I would like splunk to capture all events with timestamps in bold.&lt;BR /&gt;
Any idea how I can get around this?&lt;/ERROR_CODE&gt;&lt;/HTTP&gt;&lt;/ERROR&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:13:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106628#M27743</guid>
      <dc:creator>chiwang</dc:creator>
      <dc:date>2020-09-28T13:13:00Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple timestamps</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106629#M27744</link>
      <description>&lt;P&gt;So, I would suggest going through the following document, as I think your issue is probably more around event boundaries/line breaking than it is with timestamps: &lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Indexmulti-lineevents#How_Splunk_determines_event_boundaries" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Indexmulti-lineevents#How_Splunk_determines_event_boundaries&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;With regard to timestamps, here is another very useful document:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/latest/Data/Configuretimestamprecognition" target="_blank"&gt;http://docs.splunk.com/Documentation/Splunk/latest/Data/Configuretimestamprecognition&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It'll explain how to use TIME_PREFIX, which uses a regex to specify a pattern of what comes before the timestamp that you want to use. You'll also need to use TIME_FORMAT to specify the format of the timestamp, and MAX_TIMESTAMP_LOOKAHEAD to specify the length of the timestamp. &lt;/P&gt;

&lt;P&gt;Between these two, I think you'll find what you need. &lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:13:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106629#M27744</guid>
      <dc:creator>jbsplunk</dc:creator>
      <dc:date>2020-09-28T13:13:03Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple timestamps</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106630#M27745</link>
      <description>&lt;P&gt;I tried to get around this by providing a custom datetime.xml based on the suggestion from: &lt;A href="http://splunk-base.splunk.com/answers/1807/2-different-timestamps-in-single-log"&gt;http://splunk-base.splunk.com/answers/1807/2-different-timestamps-in-single-log&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;It worked if I manually uploaded the log file and previewed it via splunk web. The example I provided got parsed into 4 events. But once the log files got pumped in to splunk via a forwarder, multiple events are merged into one. Any other configuartion options that I should try?&lt;/P&gt;</description>
      <pubDate>Wed, 27 Feb 2013 15:57:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106630#M27745</guid>
      <dc:creator>chiwang</dc:creator>
      <dc:date>2013-02-27T15:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: Multiple timestamps</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106631#M27746</link>
      <description>&lt;P&gt;Updated with log examples. Any idea how I can get what I want? I am trying to avoid creating different log files for each log formats.&lt;/P&gt;</description>
      <pubDate>Thu, 28 Feb 2013 15:57:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Multiple-timestamps/m-p/106631#M27746</guid>
      <dc:creator>chiwang</dc:creator>
      <dc:date>2013-02-28T15:57:23Z</dc:date>
    </item>
  </channel>
</rss>

