Splunk Search

Optimize rex command

clementros
Path Finder

Hi all,

I want to extract fields form log events.

I have two errors patterns :

* Can not convert FOO from here ==> *
Can't find the FOO segment

What i want is to create a field named grammar_error_reason that contain "Can not convert FOO" or "Can't find the FOO segment"

Here is my rex command :

| rex field=CDREASON "Converted segments:(\s\w{3}+\s-)+\s(?<grammar_error_reason>.+) from here"

This command raise le limits of limits.conf. It take 236 steps.
In the limits.conf file the rex limits are :

[rex]
match_limit = 100000
depth_limit = 1000

Can you help me please.

Kind regards,
Clement

0 Karma

woodcock
Esteemed Legend

Your problem has nothing to do with limits; your problem is that your RegEx is wrong. Try this:

... | rex field=CDREASON "(?<grammar_error_reason>(?:Can not convert|Can't find the)\s+\w+)\s+(?:from here|segment)"
0 Karma

to4kawa
Ultra Champion
| makeresults 
| eval CDREASON=" * Can not convert FOO from here ==> *
 Can't find the FOO segment"
| rex field=CDREASON max_match=100 "(Can not convert|Can't find the) (?<grammar_error_reason>\w+) (from here|segment)"

HI, @clementros
How many lines per event?
If there are more than 100 lines, increase max_match values.

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!

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...