Splunk Search

Why won't my regular expression extract fields when the _raw field is greater than 56kb?

bitfhacker
New Member

Hi,

I'm trying to extract two fields with this regular expression:

Transaction\sID=\"(?P<Transaction_ID>\w*)\".*OperationCode=\"(?P<Transaction_OperationCode>\w*)\"

and it works in almost all records but it seems that when the _raw field is greater than 56kb, the regular expression doesn't work.

Any clue?

0 Karma

DalJeanis
Legend

Probably reaching catastrophic backtracking because of the greedy .* before "OperationCode=". That is going to take everything in the entire 56K until it hits the end, then back up and look for the very last place it finds "OperationCode=" before the end. Sometimes you want that behavior, but not in this case.

Instead, you want it to be lazy, and stop slurping its soup the first time it encounters "OperationCode=".

Change that middle snippet to this... we're just adding a question mark to make the .* before "OperationCode=" become "lazy" instead of "greedy".

\".*?OperationCode=\"
0 Karma

asimagu
Builder

are you able to provide a sample for the not working ones?

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!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...