Splunk Search

How to extract content between two strings?

senthamilselvan
Engager

Hi Team,

I have an error message coming up in Splunk like below. The required log message will come in the middle of the line and i have to extract the content which lies between SQL0911N & SQLSTATE=40001 .

********* SQL0911N  ##############.  SQLSTATE=40001

Can you please help us to write rex to extract the fields in between the 2 strings. Please let me know if need more information.

Thanks & Regards
Senthamilselvan J

0 Karma
1 Solution

woodcock
Esteemed Legend

Like this:

... | rex "SQL\d+N\s*(?<YouFieldNameHere>.+)\s*SQLSTATE=\d+"

View solution in original post

woodcock
Esteemed Legend

Like this:

... | rex "SQL\d+N\s*(?<YouFieldNameHere>.+)\s*SQLSTATE=\d+"

senthamilselvan
Engager

Thank you!! As of now we are getting output excluding the key values (SQL\d+N\s & SQLSTATE=\d+). But i want to display both the key values in the error message as well. Please let me know the rex to includes the key values also.

0 Karma

woodcock
Esteemed Legend

... | rex "(?SQL\d+N)\s*(?.+)\s*SQLSTATE=(?\d+)"

0 Karma

senthamilselvan
Engager

Hi Woodcock,

The search query is not working as expected, Still i am getting message excluding the two key values(SQL\d+N\s & SQLSTATE=\d).

0 Karma

somesoni2
Revered Legend

If those strings (SQL0911N & SQLSTATE=40001) are static/fixed, try like this for inline extraction in search

your base search | rex "SQL0911N\s*(?<YourFieldName>.+)\s*SQLSTATE=40001"
0 Karma
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...