Splunk Search

Disable Automatic Field Extraction

Ricapar
Communicator

Automatic field extraction is probably one of my favorite perks of throwing data into Splunk... but interestingly enough, it's causing a bit of an annoyance in this case.

I have a log that looks more or less like this:

Time: 01/02/13 01:02:58 PM
Execution Time (ms): 0.234943
Statement Text: SELECT foo, bar FROM table t WHERE t.foo="blah" AND t.bar="something" 

Pretty straight-forward - but Splunk decided to extract key/value pairs from the SQL query. Above is a rather simple query.. but the real log contains some pretty large ones with column names all over the place, thus making the "X interesting fields" list HUGE and almost impossible to find the actual fields we want to extract.

1 Solution

Ron_Naken
Splunk Employee
Splunk Employee

If you don't mind extracting the KV pairs manually for this data, you can set KV_MODE=none in props.conf for the source/sourcetype.

View solution in original post

Ron_Naken
Splunk Employee
Splunk Employee

If you don't mind extracting the KV pairs manually for this data, you can set KV_MODE=none in props.conf for the source/sourcetype.

Ricapar
Communicator

Just what I was looking for - 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!

What’s New in Splunk AI: Volume 02

Welcome to the second edition of “What’s New in Splunk AI” where we look at the latest and greatest updates, ...

Splunk App Dev Quarterly Roundup: AI, Agents, and Innovation!

Another quarter, another wave of innovation. From complex integrations to pushing the limits ...

Value Insights: Now Generally Available in the CMC

Organizations are under pressure to move faster, control cost, expand AI adoption, and prove value with more ...