Splunk Search

Fetch incident from subject

priya0709
Path Finder

I am using below query to fetch Incident from the subject line:—

rex field=subject max_match=0 “(?<Incident>INC\d+)”

however, for below subject line i am unable to fetch incident:—

[SecMail:] INC000027755501|TAS00003760220 wrdna904xusa73|server is unreachable | INC000027790458| INC000027882562

0 Karma
1 Solution

isoutamo
SplunkTrust
SplunkTrust

When I just made copy & paste from my previous example and then copy & paste both of your examples (one by one), both are working.

I suppose that you still have some issue with " or something similar.

r. Ismo

View solution in original post

0 Karma

isoutamo
SplunkTrust
SplunkTrust

Hi

I think that this is duplicate question to 

https://community.splunk.com/t5/Splunk-Search/Regex-help-for-incident/m-p/515131#M144610

basically your issue seems to be wrong  “ and ”. Otherwise your query is working as expected just switch both of those to ".

| makeresults
| eval subject="[SecMail:] INC000027755501|TAS00003760220 wrdna904xusa73|server is unreachable | INC000027790458| INC000027882562"
| rex field=subject max_match=0 "(?<Incident>INC\d+)"
| table Incident subject

r. Ismo 

0 Karma

priya0709
Path Finder

thank you for your reply!!

however, My query

rex field=subject max_match=0 "(?<Incident>INC\d+)"

works fine for Eg1 in which INC is appended by space in subject line. however, for eg2 INC is appended by | in this case Incident number is not fetched.


eg 1:- RE: INC0000756784 | server is unreachable 

eg 2:- RE:INC0000564789|Minor|server unreachable 

0 Karma

thambisetty
SplunkTrust
SplunkTrust

It doesn’t think of other characters. It matches  if there is INC FOLLOWED BY 10 digits.

————————————
If this helps, give a like below.
0 Karma

isoutamo
SplunkTrust
SplunkTrust

When I just made copy & paste from my previous example and then copy & paste both of your examples (one by one), both are working.

I suppose that you still have some issue with " or something similar.

r. Ismo

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...