<?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: How to merge events with identical timestamps into one event, but drop all differing data? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117092#M24415</link>
    <description>&lt;P&gt;Ok, this is a good start - I ran the transaction on the timestamp, as this is a performance stats collection that is running every 5 minutes on multiple devices.(Session ID's)&lt;/P&gt;

&lt;P&gt;I now have a single event that is the composite of the 9 event types.&lt;/P&gt;

&lt;P&gt;Any way to remove the duplicate null values?  (dedup on each field name?)&lt;/P&gt;</description>
    <pubDate>Wed, 10 Sep 2014 16:15:56 GMT</pubDate>
    <dc:creator>david_rundle_fi</dc:creator>
    <dc:date>2014-09-10T16:15:56Z</dc:date>
    <item>
      <title>How to merge events with identical timestamps into one event, but drop all differing data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117090#M24413</link>
      <description>&lt;P&gt;I have the following 9 events with the identical timestamps, but differing information:&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, queue_len, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, files_skipped, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, buildup_skips, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, malware_detected, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, scans_canceled, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, scans_completed, null, null, null, null, null, null, null, null, null, null, 1461, 6735, 8101, 3869, 20166, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, spf_reads, null, null, null, null, null, 1401, 6342, 8101, 3869, 19713, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, spf_writes, 1401, 6342, 8101, 3869, 19713, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null&lt;/P&gt;

&lt;P&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, spoolc_drops, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 0&lt;/P&gt;

&lt;P&gt;I want to drop the event type (spfreads, spfwrites, etc) and the null values, and combine the events into a single event.&lt;/P&gt;

&lt;P&gt;How can I do this?&lt;/P&gt;</description>
      <pubDate>Tue, 09 Sep 2014 15:04:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117090#M24413</guid>
      <dc:creator>david_rundle_fi</dc:creator>
      <dc:date>2014-09-09T15:04:38Z</dc:date>
    </item>
    <item>
      <title>Re: How to merge events with identical timestamps into one event, but drop all differing data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117091#M24414</link>
      <description>&lt;P&gt;You could probably submit some more info, especially on just how you want the combined information to look like. One thing that you might try is the &lt;CODE&gt;transaction&lt;/CODE&gt; command.&lt;/P&gt;

&lt;P&gt;Assuming that the KQ25B6P is some sort of SessionID, perhaps &lt;CODE&gt;... | transaction SessionID max_span=1s |&lt;/CODE&gt; might work for you.&lt;/P&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Tue, 09 Sep 2014 20:49:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117091#M24414</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-09-09T20:49:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to merge events with identical timestamps into one event, but drop all differing data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117092#M24415</link>
      <description>&lt;P&gt;Ok, this is a good start - I ran the transaction on the timestamp, as this is a performance stats collection that is running every 5 minutes on multiple devices.(Session ID's)&lt;/P&gt;

&lt;P&gt;I now have a single event that is the composite of the 9 event types.&lt;/P&gt;

&lt;P&gt;Any way to remove the duplicate null values?  (dedup on each field name?)&lt;/P&gt;</description>
      <pubDate>Wed, 10 Sep 2014 16:15:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117092#M24415</guid>
      <dc:creator>david_rundle_fi</dc:creator>
      <dc:date>2014-09-10T16:15:56Z</dc:date>
    </item>
    <item>
      <title>Re: How to merge events with identical timestamps into one event, but drop all differing data?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117093#M24416</link>
      <description>&lt;P&gt;Well, there is perhaps a far more attractive option;&lt;BR /&gt;
Drop the stuff you don't want (the type) by setting it to the same value everywhere, then make use of the &lt;CODE&gt;stats max()&lt;/CODE&gt; function. You may first need to replace the string 'null' with a real NULL value, if that is what you have. Or perhaps not. At least in my test you don't&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;your search | eval type = "Combined" | stats max(*) by _time
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This should look something like;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;2014-09-09 05:57:58, KQ25B6P, 7.7.1, CommandPost+, 4, 70701, Combined, 1401, 6432, 1234, 3424, 7663, 2342, null, null, 8787, 1461, 6735, 8101, 3869, 20166, null, null, null, null, null, null, null, 0, 0, 0, 0, null, null, null, null, null, null, null, null, null, 5435, 123, 0, 6676, null, null, null, null, null, 0
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;i.e. if there is a field that does not have a value in either of the events, the combined event will still have 'null'. Otherwise, the highest value will take that place.&lt;/P&gt;

&lt;P&gt;For presentation purposes you might then want play with &lt;CODE&gt;fields, replace, table, or rename&lt;/CODE&gt; etc.&lt;/P&gt;

&lt;P&gt;Hope this helps,&lt;/P&gt;

&lt;P&gt;K&lt;/P&gt;</description>
      <pubDate>Thu, 11 Sep 2014 21:32:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-merge-events-with-identical-timestamps-into-one-event-but/m-p/117093#M24416</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-09-11T21:32:52Z</dc:date>
    </item>
  </channel>
</rss>

