<?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: Indexing Semi-Unified Logs in Splunk Dev</title>
    <link>https://community.splunk.com/t5/Splunk-Dev/Indexing-Semi-Unified-Logs/m-p/352465#M5618</link>
    <description>&lt;P&gt;That's not really the idea behind ingesting data in Splunk, at least not for working with normal indexed data.&lt;/P&gt;

&lt;P&gt;Sounds like a summary index (or lookup) in which you keep the latest entry for each key might be a direction to look into.&lt;/P&gt;</description>
    <pubDate>Mon, 23 Apr 2018 13:41:48 GMT</pubDate>
    <dc:creator>FrankVl</dc:creator>
    <dc:date>2018-04-23T13:41:48Z</dc:date>
    <item>
      <title>Indexing Semi-Unified Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Indexing-Semi-Unified-Logs/m-p/352464#M5617</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;In case I have data source that sends logs to my Splunk server and some logs can be sent more than once since the data source uses semi-unified logs (original log fields + all its updates).&lt;/P&gt;

&lt;P&gt;For example:&lt;BR /&gt;
time: 10:00 am ---- log: key=0x0001; aa=1; bb=2;&lt;BR /&gt;
time:10:01 am --- log: key=0x0001; aa=2; bb=2;&lt;/P&gt;

&lt;P&gt;Is there any option to delete the old log when identifying a new log with the same key?&lt;/P&gt;

&lt;P&gt;Thanks &lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 09:19:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Indexing-Semi-Unified-Logs/m-p/352464#M5617</guid>
      <dc:creator>shayhibah</dc:creator>
      <dc:date>2018-04-23T09:19:48Z</dc:date>
    </item>
    <item>
      <title>Re: Indexing Semi-Unified Logs</title>
      <link>https://community.splunk.com/t5/Splunk-Dev/Indexing-Semi-Unified-Logs/m-p/352465#M5618</link>
      <description>&lt;P&gt;That's not really the idea behind ingesting data in Splunk, at least not for working with normal indexed data.&lt;/P&gt;

&lt;P&gt;Sounds like a summary index (or lookup) in which you keep the latest entry for each key might be a direction to look into.&lt;/P&gt;</description>
      <pubDate>Mon, 23 Apr 2018 13:41:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Dev/Indexing-Semi-Unified-Logs/m-p/352465#M5618</guid>
      <dc:creator>FrankVl</dc:creator>
      <dc:date>2018-04-23T13:41:48Z</dc:date>
    </item>
  </channel>
</rss>

