Getting Data In

How to search data usage by sourcetype

anil1432
Explorer

Hello everyone, 

 

I need  query to find out 

sourcetype =gshshsh

is using how much of data  

1. From February month day wise usage.  and

2. From September to February month data  usage

Labels (1)
0 Karma

tshah-splunk
Splunk Employee
Splunk Employee

Hi @anil1432,

I couldn't understand much of what do you mean by data usage?

If this is in the context of license usage based on sourcetype, you can navigate to Monitoring Console -> Indexing -> License Usage -> License Usage - Previous 30 days dashboard and filter the data to display the dashboard split by "sourcetype". And since it is based on timechart, you can find the usage for different periods of time as per your need. 

 

If this is in the context of event count based on sourcetype, you can run the following search query between specific time intervals to get the count of events for that specific sourcetype for the defined time interval

| metadata type=sourcetypes index=* splunk_server_group=dmc_group_indexer splunk_server_group="*"
| fields sourcetype, totalCount
| sort - totalCount
| search sourcetype=gshshsh
| rename sourcetype as Sourcetype, totalCount as "Event Count" 
---
If you find the answer helpful, an upvote/karma is appreciated
0 Karma
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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...