Splunk Search

why does the results from 'eventscount' and displayed DDAS storage usage in CloudMonitoring Console differ wildly?

Falko
Explorer

I tried to determine the size of my indexes in preparation for a Splunk Cloud Migration. I figured I could use the "eventcount" command to summarise the used index storage:



| eventcount summarize=true index=* report_size=true | eval sizeGB=round((size_bytes/1024/1024/1024),2) | eval ddasUnits=(sizeGB/500) 

 

Then I let this command also run in one of my existing Splunk Cloud stack and expected the number to roughly match what the SPlunk Cloud Monitoring console would display for DDAS storage usage. But the numbers differ wildly. Eventcount reports something like 323 TB and DDAS usage reports 590 TB. 

Wh

Labels (1)
Tags (3)
0 Karma
Get Updates on the Splunk Community!

Enhance Your Splunk App Development: New Tools & Support

UCC FrameworkAdd-on Builder has been around for quite some time. It helps build Splunk apps faster, but it ...

Prove Your Splunk Prowess at .conf25—No Prereqs Required!

Your Next Big Security Credential: No Prerequisites Needed We know you’ve got the skills, and now, earning the ...

Splunk Observability Cloud's AI Assistant in Action Series: Observability as Code

This is the sixth post in the Splunk Observability Cloud’s AI Assistant in Action series that digs into how to ...