Installation

How do I determine my indexing volume by host, source, or sourcetype?

matt
Splunk Employee
Splunk Employee

I need to know the breakdown of my license consumption on a per host, per source, and per sourcetype basis. What is the search to do this?

Labels (1)
1 Solution

ziegfried
Influencer

per host:

index="_internal" source="*metrics.log" group="per_host_thruput" | chart sum(kb) by series | sort - sum(kb)

per source:

index="_internal" source="*metrics.log" group="per_source_thruput" | chart sum(kb) by series | sort - sum(kb)

per sourcetype:

index="_internal" source="*metrics.log" group="per_sourcetype_thruput" | chart sum(kb) by series | sort - sum(kb)

View solution in original post

wharmsworth
Engager
index=_internal source="*license_usage.log" type=usage type=Usage idx=* pool="Your Pool Name" earliest=-30d@d latest=@d
| eval GB = b
| timechart limit=50 partial=false span=1d sum(eval(GB/1024/1024/1024)) by idx

This works well for me.

0 Karma

sideview
SplunkTrust
SplunkTrust

In the search app that Splunk ships with, under 'Status', there is a view called 'Indexing volume'. Go there and you'll see that it offers precisely this -- you can see your indexing volume broken down over time by source, by sourcetype, by host or by index.

Some raw searches themselves are posted in another answer but you'll probably find the custom view the most useful.

damode
Motivator

Hi @sideview,
Can you please point where exactly the status option is displayed on the Search and Reporting page of Splunk ?

Thanks

0 Karma

ziegfried
Influencer

per host:

index="_internal" source="*metrics.log" group="per_host_thruput" | chart sum(kb) by series | sort - sum(kb)

per source:

index="_internal" source="*metrics.log" group="per_source_thruput" | chart sum(kb) by series | sort - sum(kb)

per sourcetype:

index="_internal" source="*metrics.log" group="per_sourcetype_thruput" | chart sum(kb) by series | sort - sum(kb)

Simeon
Splunk Employee
Splunk Employee
0 Karma

Simeon
Splunk Employee
Splunk Employee

While the above search will work for most cases, only the top 10 values over 30 second periods are indexed by default. For this reason, you may not see low volume hosts populating the search results. You can increase the number of data points for the metrics.log file by editing the samples taken within limits.conf. See the following link and look for "metrics":

http://www.splunk.com/base/Documentation/latest/Admin/Limitsconf

Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...