Splunk Search

Regex for field extraction

splunkn
Communicator

I am having a source file with the two below mentioned format. However I need to extract a same field but whose positions differ.
Could anyone help me with appropriate regex?

Jan 21 19:38:53 hostname sudo: pam_unix(sudo:session): session opened for user abc by xyz(uid=0)

Jan 21 19:38:38 hostname sshd[000]: Accepted password for xyz from port 123

Here I need to extract the user "xyz" . Both events belongs to same source. How could write the regex to match the both?

OR do we need to go with Field alias?

Thanks in advance

Tags (2)
0 Karma
1 Solution

pradeepkumarg
Influencer

One way is to extract both differently and then use coalesce function to grab the one that is not NULL

... |  rex "(?i)session opened for user \w+ by (?P<USER1>.\w+)\W"  |  rex "(?i)Accepted password for(?P<USER2>.\w+) from" 
    | eval USER = coalesce(USER1,USER2)

View solution in original post

0 Karma

pradeepkumarg
Influencer

One way is to extract both differently and then use coalesce function to grab the one that is not NULL

... |  rex "(?i)session opened for user \w+ by (?P<USER1>.\w+)\W"  |  rex "(?i)Accepted password for(?P<USER2>.\w+) from" 
    | eval USER = coalesce(USER1,USER2)
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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...