Getting Data In

Why is indexing volume not matching license usage?

leonards1
Explorer

Following some runaway license violations, I am looking to find the offending host but in running the queries that I have, I am finding that the total "host usage" is far more than the "license usage".

I am using the following to show the usage per host:

index="_internal" source="*metrics.log" group="per_host_thruput" | eval mb = (round(kb,0)/1024) |chart sum(mb) by series | sort - sum(mb)

I am using the following to find the usage against the license:

index=_internal source=*license_usage* type=RolloverSummary  | bucket _time span=1d | eval MB_vol=b/1024/1024 | timechart span=1d sum(MB_vol) by pool

Is this correct? Is this related to this post? -- https://answers.splunk.com/answers/2886/indexing-volume-vs-data-size-received.html?utm_source=typeah...

0 Karma
1 Solution

masonmorales
Influencer

type=RolloverSummary will only show the top 10 indexes. To see the total by host you can do something like:

index="_internal" source=*license_usage.log type=Usage | eval KB=round(b/1024) | eval MB=round(KB/1024,2) | eval GB=round(MB/1024,2) | eval TB=round(GB/1024,2) | stats sum(MB) as Total by h

Or by pool and day:

index=_internal source=*license_usage* type=Usage | bucket _time span=1d | eval MB_vol=b/1024/1024 | stats (MB_vol) by pool _time

View solution in original post

0 Karma

masonmorales
Influencer

type=RolloverSummary will only show the top 10 indexes. To see the total by host you can do something like:

index="_internal" source=*license_usage.log type=Usage | eval KB=round(b/1024) | eval MB=round(KB/1024,2) | eval GB=round(MB/1024,2) | eval TB=round(GB/1024,2) | stats sum(MB) as Total by h

Or by pool and day:

index=_internal source=*license_usage* type=Usage | bucket _time span=1d | eval MB_vol=b/1024/1024 | stats (MB_vol) by pool _time
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...