Splunk Search

Why is the following regex expression not matching as expected?

SunilMaharishi
Path Finder

I have a field user= xyz\user11 and i need to match user11 ignoring xyz in the user filed

below is the regex expression we have been trying but it gives error as unmatched parenthesis or some other and Result field is not available in the logs if it runs successfully .

rex field=user (?\w+\\(\w+))
Tags (2)
0 Karma
1 Solution

pjnike
Engager

You have to specify which field to extract the value to. Also, the backslash(\) before opening parenthesis in your query escapes the ( which causes Splunk to give an error of unmatched parenthesis. You need to escape the backslash with \.

Try this: rex field=user "\w+\\\(?<user_name>\w+)"

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust

We can't read your rex string because the forum mangled it. To prevent this, put code, HTML, and SPL inside backticks or use the code button (101010).

Backslashes require extra escape characters in regex strings within SPL. Try rex field=user "\\\(?<Result>.*)".

---
If this reply helps you, Karma would be appreciated.
0 Karma

pjnike
Engager

You have to specify which field to extract the value to. Also, the backslash(\) before opening parenthesis in your query escapes the ( which causes Splunk to give an error of unmatched parenthesis. You need to escape the backslash with \.

Try this: rex field=user "\w+\\\(?<user_name>\w+)"

0 Karma

SunilMaharishi
Path Finder

that was mistyped fieldname was specified though

but it is working now thank you

0 Karma
Get Updates on the Splunk Community!

Update Your SOAR Apps for Python 3.13: What Community Developers Need to Know

To Community SOAR App Developers - we're reaching out with an important update regarding Python 3.9's ...

October Community Champions: A Shoutout to Our Contributors!

As October comes to a close, we want to take a moment to celebrate the people who make the Splunk Community ...

Automatic Discovery Part 2: Setup and Best Practices

In Part 1 of this series, we covered what Automatic Discovery is and why it’s critical for observability at ...