Installation

Restrict data to be indexed

nrelihan
Explorer

Hi, Im looking to find a remedy to restict the data that is being indexed by splunk to just error messages. The reason being is the data being indexed by a particular host is exceeding what my license allows. I believe there are particular config files that can be modified to do this?

Thanks

0 Karma
1 Solution

sdwilkerson
Contributor

nrelihan,

What you are looking for is the nullQueue in Splunk. Essentially you use your parsing configs to determine what events should be deleted or preserved, depending on your situation.

You can find instructions in the docs, and there are many answers already posted that might address your specific needs.

Sean

View solution in original post

sdwilkerson
Contributor

nrelihan,

What you are looking for is the nullQueue in Splunk. Essentially you use your parsing configs to determine what events should be deleted or preserved, depending on your situation.

You can find instructions in the docs, and there are many answers already posted that might address your specific needs.

Sean

nrelihan
Explorer

Thats great Sean, exactly what I'm looking for, I'll have to do a bit of reading to wrap my head around it. thanks.

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!

Introducing ITSI 5.0: Unified Visibility and Actionable Insights

Introducing ITSI 5.0: Unified Visibility and Actionable Insights Tuesday, July 21, 2026  |  10:00AM PT / ...

Inside Splunk Agent Observability: Understanding Agent Behavior, Tokens & Costs

Inside Splunk Agent Observability:Understanding Agent Behavior, Tokens & Costs Thursday, August 06, ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...