Splunk Search

Automatic field extractions from a quoted string

sfrazer
Explorer

Our nginx access logs use a quoted string when dumping cookies. It ends up looking something like this:

"cookie_a=value_a; cookie_b=value_b; cookie_c=value_c" 192.168.1.1 

The trouble comes when the auto-extractor hits cookie_c and sees the quote as the beginning of a quoted string. It then gobbles up all the fields after the cookie and dumps them into that field. Because cookie order isn't deterministic, you end up with a certain percentage of cookie_c values that are correct and a smaller number that are not.

Is there anyway to offer a hint to the auto-extractor to make this not happen?

0 Karma

stephanefotso
Motivator

Yes of course! your can create your search time field extraction with props.conf edit.
Let's suppose that The field should be extracted from events related to the accesslogs sourcetype.
1. Create your own props.conf file, and put it in $SPLUNK_HOME/etc/apps/yourappname/local.
2. configure your stanza like this:

[acceslogs]
EXTRACT-cookiec = cookie_c=(?<cookie_c>[^"]+)
  1. and restart splunk
SGF
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!

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

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...