Splunk Search

REGEX Extraction for btool.log

hartfoml
Motivator

I have these btool logs:

10-29-2013 09:15:34.551 INFO AdminManager - added factory for admin handler: 'licenses'
10-29-2013 09:15:34.551 DEBUG AdminManager - Found path '/opt/splunk/etc/apps/search/bin' for handler 'sendemail'.
29-2013 09:15:34.551 DEBUG HTTPRestDispatcher - loadConfig for masterlm _isProServer=1

When I do the automated extraction if looks like this:

(?i) DEBUG (?P<FIELDNAME>[^ ]+)

This does not find the valus followed by INFO. How could I right this so it is not dependent on the word "DEBUG"

Tags (1)
0 Karma
1 Solution

gfuente
Motivator

Hello

try this:

(?i) (DEBUG|INFO) (?P<FIELDNAME>[^ ]+)

And add with pipes any other severity values you would like to capture

regards

View solution in original post

gfuente
Motivator

Hello

try this:

(?i) (DEBUG|INFO) (?P<FIELDNAME>[^ ]+)

And add with pipes any other severity values you would like to capture

regards

hartfoml
Motivator

Thanks again for the help.

I should have put in the things I tried at the beginning.

I tried (?i) \w+ (?P<fieldname>[^ ]+)
and this (?i) \w+\s (?P<fieldname>[^ ]+)
and this (?i)\w+\s(?P<fieldname>[^ ]+)\s\-\s

0 Karma

gfuente
Motivator

then use this:

(?i) \w+ (?P<FIELDNAME>[^ ]+)

There is a "\" before the w+

0 Karma

hartfoml
Motivator

Right Thanks, I did think of doing this but what if there is a WARN or ERROR. I didn't want to put (DEBUG|ERROR|WARN|INFO) I was hoping for a more elegant way to right it.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...