<?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 Unique Contraint in Splunk in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507186#M86307</link>
    <description>&lt;P&gt;We have a number of files containing events. Each event has a unique id in itself. but the same event(with the same event_id) can exist in other files as well. We want 1 event to be indexed 1 time in Splunk and if the event with the same event_id comes again just avoid it. This is the same as _id in Elastic Search or another database's primary key.&lt;/P&gt;&lt;P&gt;Is it possible to achieve the same in Splunk? If yes, How?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 03 Jul 2020 05:21:16 GMT</pubDate>
    <dc:creator>akshgpt25</dc:creator>
    <dc:date>2020-07-03T05:21:16Z</dc:date>
    <item>
      <title>Unique Contraint in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507186#M86307</link>
      <description>&lt;P&gt;We have a number of files containing events. Each event has a unique id in itself. but the same event(with the same event_id) can exist in other files as well. We want 1 event to be indexed 1 time in Splunk and if the event with the same event_id comes again just avoid it. This is the same as _id in Elastic Search or another database's primary key.&lt;/P&gt;&lt;P&gt;Is it possible to achieve the same in Splunk? If yes, How?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jul 2020 05:21:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507186#M86307</guid>
      <dc:creator>akshgpt25</dc:creator>
      <dc:date>2020-07-03T05:21:16Z</dc:date>
    </item>
    <item>
      <title>Re: Unique Contraint in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507187#M86308</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/223240"&gt;@akshgpt25&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Not sure it is possible during indexing, but you can get unique event in SPL by using dedup command.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.0.4/SearchReference/Dedup" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.0.4/SearchReference/Dedup&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jul 2020 05:32:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507187#M86308</guid>
      <dc:creator>kamlesh_vaghela</dc:creator>
      <dc:date>2020-07-03T05:32:05Z</dc:date>
    </item>
    <item>
      <title>Re: Unique Contraint in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507188#M86309</link>
      <description>&lt;P&gt;Thanks,&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/127939"&gt;@kamlesh_vaghela&lt;/a&gt;&amp;nbsp;&lt;SPAN class="login-bold"&gt;for the quick response.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;But we have millions of events with this behavior and every time end-user have to use dedup in all their queries.&lt;/P&gt;&lt;P&gt;Is there any other way to achieve the same?&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jul 2020 05:38:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507188#M86309</guid>
      <dc:creator>akshgpt25</dc:creator>
      <dc:date>2020-07-03T05:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unique Contraint in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507199#M86312</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/223240"&gt;@akshgpt25&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;as&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/127939"&gt;@kamlesh_vaghela&lt;/a&gt;&amp;nbsp; said it isn't possible to filter events before indexing to avoid duplicates, but you could ingest all the data and schedule a search that extract the unduplicated events and store them in a summary_index, then you can use this index for your searches.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jul 2020 06:50:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507199#M86312</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2020-07-03T06:50:27Z</dc:date>
    </item>
    <item>
      <title>Re: Unique Contraint in Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507201#M86313</link>
      <description>&lt;P&gt;I'm not sure if this can first validate if an event is in Splunk before it routes data to Splunk and I don't know a great deal about it, but the DSP component may do what you want&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.splunk.com/en_us/software/stream-processing.html" target="_blank"&gt;https://www.splunk.com/en_us/software/stream-processing.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 03 Jul 2020 06:54:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Unique-Contraint-in-Splunk/m-p/507201#M86313</guid>
      <dc:creator>bowesmana</dc:creator>
      <dc:date>2020-07-03T06:54:04Z</dc:date>
    </item>
  </channel>
</rss>

