Getting Data In

License usage for one index broken down by sourcetype

ddrillic
Ultra Champion

How can I get a license usage for one index broken down by sourcetype? I know this question came up recently in different manifestations ; -) sorry.

0 Karma
1 Solution

somesoni2
Revered Legend

Try this

index=_internal sourcetype=splunkd source=*license_usage.log type=Usage idx=YourIndexHere
| stats sum(b) as usage by idx st | eval usage_MB=round(usage/1024/1024,3)
| rename idx and index st as sourcetype

View solution in original post

DalJeanis
Legend

Start here -

index=_internal source=*license_usage.log* Usage 
| eval s=coalesce(s,"unknown"), eval st=coalesce(st,"unknown") 
|  stats sum(b) as bytes by idx s st

micahkemp
Champion
index=_internal source="*/license_usage.log" component=LicenseUsage idx=<your index>
| timechart sum(b) AS b BY st

In the license usage events idx is the index and st is the sourcetype that the licensing metrics are detailing.

somesoni2
Revered Legend

Try this

index=_internal sourcetype=splunkd source=*license_usage.log type=Usage idx=YourIndexHere
| stats sum(b) as usage by idx st | eval usage_MB=round(usage/1024/1024,3)
| rename idx and index st as sourcetype

elliotproebstel
Champion

If you find yourself needing to break out license usage statistics often, you might find it helpful to check out the License Usage app, which includes queries for license usage by index/sourcetype/etc.

https://splunkbase.splunk.com/app/174/#/overview

But in particular, this question had a good answer that breaks out license usage by indexname and sourcetype:
https://answers.splunk.com/answers/417031/license-usage-by-source-type.html

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...