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 (2)
Tags (3)
0 Karma
Get Updates on the Splunk Community!

Take Your Breath Away with Splunk Risk-Based Alerting (RBA)

WATCH NOW!The Splunk Guide to Risk-Based Alerting is here to empower your SOC like never before. Join Haylee ...

SignalFlow: What? Why? How?

What is SignalFlow? Splunk Observability Cloud’s analytics engine, SignalFlow, opens up a world of in-depth ...

Federated Search for Amazon S3 | Key Use Cases to Streamline Compliance Workflows

Modern business operations are supported by data compliance. As regulations evolve, organizations must ...