<?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: Splunk treating multiple lines as one event since they have the same timestamp in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71049#M17776</link>
    <description>&lt;P&gt;thanks for the response.&lt;/P&gt;

&lt;P&gt;I did that, but it did not resolve the problem for existing events. Do I need to delete the data and re-import it into splunk for the fix to take effect&lt;/P&gt;</description>
    <pubDate>Fri, 22 Mar 2013 20:59:25 GMT</pubDate>
    <dc:creator>sourabhguha</dc:creator>
    <dc:date>2013-03-22T20:59:25Z</dc:date>
    <item>
      <title>Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71046#M17773</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I have the following events. You can see that the timestamps are the same to the second. Due to this Splunk seems to be treating them as one event. However, each is a discrete event. How can i have splunk treat them as discrete events?&lt;/P&gt;

&lt;P&gt;9B4C74AF-24D5-45EC-B250-E0B3815F8744,twi1gjni2q.database.windows.net,: Database,DB Number Sessions,20,2013-03-22 02:48:17.003&lt;BR /&gt;
F4FEF78F-FBEF-4201-B0B1-02B0221099C5,twi1gjni2q.database.windows.net,: Database,DB Network Internal Egress (KB),17740.686528,2013-03-22 02:48:17.030&lt;BR /&gt;
0014E747-4BCB-4542-9B5B-A6D7CE9D0110,qa84z9y1vj.database.windows.net,: Database,DB Total Used Space (%),28.9451599121094,2013-03-22 02:48:17.997&lt;BR /&gt;
D7448FB8-2CBB-4F54-B229-81E6BD3B604C,qa84z9y1vj.database.windows.net,: Database,DB Total Free Space (%),71.0548400878906,2013-03-22 02:48:18.013&lt;BR /&gt;
D744C4C8-1C49-4075-A47F-19F0D6B04533,qa84z9y1vj.database.windows.net,: Database,DB Total Used Space (MB),296.3984375,2013-03-22 02:48:18.023&lt;BR /&gt;
0A95EAE0-D7B9-428F-826E-0D4D6341CD2D,qa84z9y1vj.database.windows.net,: Database,DB Total Space Quota (MB),1024,2013-03-22 02:48:18.030&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2013 04:10:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71046#M17773</guid>
      <dc:creator>sourabhguha</dc:creator>
      <dc:date>2013-03-22T04:10:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71047#M17774</link>
      <description>&lt;P&gt;Hi sourabhguha,(amended from previous answer)&lt;/P&gt;

&lt;P&gt;Have you set up a props.conf file for this data as you can add a config that will break each line up as a different.&lt;/P&gt;

&lt;P&gt;I have just been testing with the data that you have and have been able to get it working by adding the TIME_PREFIX option to the props.conf and adding a comma, as listed below:&lt;BR /&gt;
TIME_PREFIX=,&lt;/P&gt;

&lt;P&gt;If this does not work, let me know what you props.conf file looks like and I would be glad to work on it further with you.&lt;/P&gt;

&lt;P&gt;Regards Vince&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:34:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71047#M17774</guid>
      <dc:creator>vincesesto</dc:creator>
      <dc:date>2020-09-28T13:34:47Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71048#M17775</link>
      <description>&lt;P&gt;You should also be looking to set &lt;CODE&gt;TIME_FORMAT&lt;/CODE&gt; and &lt;CODE&gt;MAX_TIMESTAMP_LOOKAHEAD&lt;/CODE&gt; in &lt;CODE&gt;props.conf&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;Also, you should benefit from setting &lt;CODE&gt;SHOULD_LINEMERGE=false&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;/K&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 13:34:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71048#M17775</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2020-09-28T13:34:52Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71049#M17776</link>
      <description>&lt;P&gt;thanks for the response.&lt;/P&gt;

&lt;P&gt;I did that, but it did not resolve the problem for existing events. Do I need to delete the data and re-import it into splunk for the fix to take effect&lt;/P&gt;</description>
      <pubDate>Fri, 22 Mar 2013 20:59:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71049#M17776</guid>
      <dc:creator>sourabhguha</dc:creator>
      <dc:date>2013-03-22T20:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71050#M17777</link>
      <description>&lt;P&gt;No. Already indexed events cannot be altered in that respect. There are a few types of information that cannot (almost) be changed on already indexed data, e.g. timestamp, index, source, host, sourcetype, and in your case event-breaking&lt;/P&gt;</description>
      <pubDate>Sat, 23 Mar 2013 08:17:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71050#M17777</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2013-03-23T08:17:09Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71051#M17778</link>
      <description>&lt;P&gt;Hi sourabhguha, if you do reindex your data, I would be interested to know if it works or now?&lt;BR /&gt;
Regards Vince&lt;/P&gt;</description>
      <pubDate>Sat, 23 Mar 2013 08:39:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71051#M17778</guid>
      <dc:creator>vincesesto</dc:creator>
      <dc:date>2013-03-23T08:39:59Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk treating multiple lines as one event since they have the same timestamp</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71052#M17779</link>
      <description>&lt;P&gt;hi Vince, i did reindex my data with the option you suggested and it worked. thanks for your help!&lt;/P&gt;</description>
      <pubDate>Mon, 25 Mar 2013 02:44:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Splunk-treating-multiple-lines-as-one-event-since-they-have-the/m-p/71052#M17779</guid>
      <dc:creator>sourabhguha</dc:creator>
      <dc:date>2013-03-25T02:44:34Z</dc:date>
    </item>
  </channel>
</rss>

