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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...