Splunk Search

How to auto dynamically extract all keyN to fields?

jbanAtSplunk
Communicator

Hi,

I have a log that will dynamically add "fields" to log record based on some logic.

It's syslog begging + payload that looks like (example)

Sep 10 16:52:07 11.11.11.11 Sep 10 16:52:07 process[111]: app=test&key0=value0&key1=value1&key2=key...&keyN=valueN

how to automatically/dynamically extract all keyN to fields.

Labels (1)
0 Karma
1 Solution

yuanliu
SplunkTrust
SplunkTrust

How is the props.conf section for this sourcetype? (Also see Field extraction configuration especially KV_MODE.)  It is rather strange that Splunk doesn't already extract all pairs separated by =.

View solution in original post

0 Karma

jbanAtSplunk
Communicator

checked under the hood, looks like there is sourcetype transformations so that stanza didn't have KV_MODE.
I put KV_MODE=auto_escaped and it'll extract it automatically.

0 Karma

yuanliu
SplunkTrust
SplunkTrust

How is the props.conf section for this sourcetype? (Also see Field extraction configuration especially KV_MODE.)  It is rather strange that Splunk doesn't already extract all pairs separated by =.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...