<?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 Cloud DDAS / delete? in Splunk Cloud Platform</title>
    <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692091#M3122</link>
    <description>&lt;P&gt;No. Splunk Cloud "underneath" is essentially the same indexing and searching machinery embedded within some additional management layer. So the delete command works exactly the same - it masks the data as "unreachable". It doesn't change anything else - the data has already been ingested so it counts against your license entitlement.&lt;/P&gt;</description>
    <pubDate>Mon, 01 Jul 2024 13:02:27 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2024-07-01T13:02:27Z</dc:date>
    <item>
      <title>Splunk Cloud DDAS / delete?</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692048#M3120</link>
      <description>&lt;P&gt;We all know that Splunk Enterprise calculates license usage at index time, and the "| delete" command essentially just hides data from search so doesn't free up license usage.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;My question is whether this works the same way for Splunk Cloud / DDAS, or whether if I run "| delete" from search,&amp;nbsp; will it free up space in my DDAS entitlement?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 04:08:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692048#M3120</guid>
      <dc:creator>KendallW</dc:creator>
      <dc:date>2024-07-01T04:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud DDAS / delete?</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692064#M3121</link>
      <description>&lt;P&gt;The delete command essentially works in the same way in Splunk Cloud as it does in an on-prem infrastructure. It won't delete your data from DDAS, but will make it unsearchable.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 09:49:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692064#M3121</guid>
      <dc:creator>shivanshu1593</dc:creator>
      <dc:date>2024-07-01T09:49:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Cloud DDAS / delete?</title>
      <link>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692091#M3122</link>
      <description>&lt;P&gt;No. Splunk Cloud "underneath" is essentially the same indexing and searching machinery embedded within some additional management layer. So the delete command works exactly the same - it masks the data as "unreachable". It doesn't change anything else - the data has already been ingested so it counts against your license entitlement.&lt;/P&gt;</description>
      <pubDate>Mon, 01 Jul 2024 13:02:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Cloud-Platform/Splunk-Cloud-DDAS-delete/m-p/692091#M3122</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-07-01T13:02:27Z</dc:date>
    </item>
  </channel>
</rss>

