Getting Data In

Searching w/o Indexing

jam678
Explorer

Is there a way to access SplunkWeb without turning on indexing? My license just got crushed by a security audit team, and we're going way over our license each day as the logs play catch-up. After a while it should return to normal, but is there any way to access the data by say, stopping indexing before I go over the license limit?

1 Solution

jbsplunk
Splunk Employee
Splunk Employee

Not really, but I think there is a better way to resolve this situation than turning off indexing. If you're an enterprise customer you're allowed 5 violations within a 30 day rolling window, so a couple of violations shouldn't be a big deal. Additionally, running with the same presumption, you can request a license reset from support/sales.

The thing to do here is determine what is causing the violations with the searches you can find here:

http://wiki.splunk.com/Community:TroubleshootingIndexedDataVolume

Take a look at the section that says 'Quick summary information by host, source, source type, and index', it'll give you some searches that will identify broadly the areas where you're volume is being used.

From there use the information at this link to route unnecessary

http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Routeandfilterdatad

The section you're looking for is 'Filter event data and send to queues'.

You can eliminate unwanted data by routing it to nullQueue, Splunk's /dev/null equivalent. When you filter out data in this way, the filtered data is not forwarded or added to the Splunk index at all, and doesn't count toward your indexing volume. 

View solution in original post

0 Karma

jbsplunk
Splunk Employee
Splunk Employee

Not really, but I think there is a better way to resolve this situation than turning off indexing. If you're an enterprise customer you're allowed 5 violations within a 30 day rolling window, so a couple of violations shouldn't be a big deal. Additionally, running with the same presumption, you can request a license reset from support/sales.

The thing to do here is determine what is causing the violations with the searches you can find here:

http://wiki.splunk.com/Community:TroubleshootingIndexedDataVolume

Take a look at the section that says 'Quick summary information by host, source, source type, and index', it'll give you some searches that will identify broadly the areas where you're volume is being used.

From there use the information at this link to route unnecessary

http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Routeandfilterdatad

The section you're looking for is 'Filter event data and send to queues'.

You can eliminate unwanted data by routing it to nullQueue, Splunk's /dev/null equivalent. When you filter out data in this way, the filtered data is not forwarded or added to the Splunk index at all, and doesn't count toward your indexing volume. 
0 Karma

jbsplunk
Splunk Employee
Splunk Employee

Your understanding is correct, you won't stop indexing at whatever your indexing limit is, just incur a violation. Even if you had 6 violations, search would be the only thing affected.

0 Karma

jam678
Explorer

Thanks, that should work - didn't know about directing data to /dev/null, that should be a huge help.

There aren't any limitations to how much over the license you can go in one day, right? Say I have a 10GB License, I can index, say, 50GB that one day as long as I don't do it 5 times over 30 days?

0 Karma
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 ...