<?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 Delete indexed event and prevent from indexed again? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Delete-indexed-event-and-prevent-from-indexed-again/m-p/320353#M59799</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I developing a Table dashboard with new data populated every 10 seconds using DBX. For some private reasons, I cannot use Rising Column of DBX, so there many duplicated events.&lt;/P&gt;

&lt;P&gt;I also use Javascript to let the user to remove one or some row in the table. My current dummy strategy is:&lt;BR /&gt;
1. Export the to-be-removed event to csv file using &lt;CODE&gt;outputcsv&lt;/CODE&gt; command&lt;BR /&gt;
2. Running a &lt;CODE&gt;delete&lt;/CODE&gt; command&lt;BR /&gt;
3. On the next refresh, compare with the csv file and eliminate the events with the same with removed event.&lt;/P&gt;

&lt;P&gt;I must pause the dashboard refreshing to let the &lt;CODE&gt;outputcsv&lt;/CODE&gt; complete or the &lt;CODE&gt;removed&lt;/CODE&gt; event may re-appear because of the duplication. The problem is that &lt;CODE&gt;outputcsv&lt;/CODE&gt; and the comparing process take very long to complete - which affect user experiences.&lt;/P&gt;

&lt;P&gt;I want to ask if there is any neat way to mark the events as &lt;CODE&gt;deleted&lt;/CODE&gt; and prevent it to be indexed again? Can I edit the indexed events and mark them as I wish?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Thu, 05 Apr 2018 04:17:16 GMT</pubDate>
    <dc:creator>nhgiang1994</dc:creator>
    <dc:date>2018-04-05T04:17:16Z</dc:date>
    <item>
      <title>Delete indexed event and prevent from indexed again?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-indexed-event-and-prevent-from-indexed-again/m-p/320353#M59799</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;I developing a Table dashboard with new data populated every 10 seconds using DBX. For some private reasons, I cannot use Rising Column of DBX, so there many duplicated events.&lt;/P&gt;

&lt;P&gt;I also use Javascript to let the user to remove one or some row in the table. My current dummy strategy is:&lt;BR /&gt;
1. Export the to-be-removed event to csv file using &lt;CODE&gt;outputcsv&lt;/CODE&gt; command&lt;BR /&gt;
2. Running a &lt;CODE&gt;delete&lt;/CODE&gt; command&lt;BR /&gt;
3. On the next refresh, compare with the csv file and eliminate the events with the same with removed event.&lt;/P&gt;

&lt;P&gt;I must pause the dashboard refreshing to let the &lt;CODE&gt;outputcsv&lt;/CODE&gt; complete or the &lt;CODE&gt;removed&lt;/CODE&gt; event may re-appear because of the duplication. The problem is that &lt;CODE&gt;outputcsv&lt;/CODE&gt; and the comparing process take very long to complete - which affect user experiences.&lt;/P&gt;

&lt;P&gt;I want to ask if there is any neat way to mark the events as &lt;CODE&gt;deleted&lt;/CODE&gt; and prevent it to be indexed again? Can I edit the indexed events and mark them as I wish?&lt;/P&gt;

&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 05 Apr 2018 04:17:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-indexed-event-and-prevent-from-indexed-again/m-p/320353#M59799</guid>
      <dc:creator>nhgiang1994</dc:creator>
      <dc:date>2018-04-05T04:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: Delete indexed event and prevent from indexed again?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Delete-indexed-event-and-prevent-from-indexed-again/m-p/320354#M59800</link>
      <description>&lt;P&gt;I think the best way to delete the events and prevent it t be indexed again is to send it to &lt;CODE&gt;nullqueue&lt;/CODE&gt;. &lt;/P&gt;

&lt;P&gt;Refer this document for more information&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/7.0.3/Forwarding/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest"&gt;http://docs.splunk.com/Documentation/Splunk/7.0.3/Forwarding/Routeandfilterdatad#Discard_specific_events_and_keep_the_rest&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;This will make changes in real time and future events this will not change the data which is already indexed i.e. historical events that you need to delete using &lt;CODE&gt;| delete&lt;/CODE&gt; command.&lt;/P&gt;

&lt;P&gt;Let me know if this helps!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Apr 2018 06:45:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Delete-indexed-event-and-prevent-from-indexed-again/m-p/320354#M59800</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-04-05T06:45:09Z</dc:date>
    </item>
  </channel>
</rss>

