All Apps and Add-ons

Field Extraction Stops Working

corwinz6
Explorer

I want to associate the IP address included in the logs that refers to the device the log came from to a field. i.e:

Nov 12 16:04:21 x.x.x.x date=2012-11-12 time=16:03:21

where x.x.x.x is the IP I want included in the new field. When I use the interactive field extractor sometimes it gives me:

(?i)^(?:[^ ]* ){3}(?P<FIELDNAME>[^ ]+)

which works for a week or two and then stops.

If I use the extractor again it then gives me a slightly different output of:

(?i)^(?:[^ ]* ){4}(?P<FIELDNAME>[^ ]+)

This one then works for a time and I have to end up changing it back to the {3} extraction and so on. I'm not very regex savvy, is there someone who could assist me with a regex string that will consistently grab that field?

Thanks

0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

The field extractor regex basically counts the number of spaces before the IP. During the first nine days of the month there is an extra space, compare:

Nov  9 01:02:03 x.x.x.x
Nov 10 01:02:03 x.x.x.x

However, what you want is "three words before the IP", not "three (or four) spaces before the IP". Try something like this untested extraction:

^(?:[^\s]+\s+){3}(?P<FIELDNAME>(\d{1,3}\.){3}\d{1,3})

This looks for "positive number of non-spaces followed by positive number of spaces" (read: "words") three times, then picks out the IP while taking the decimal notation into account. Note, this would allow invalid IPs such as "999.999.999.999".

View solution in original post

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

The field extractor regex basically counts the number of spaces before the IP. During the first nine days of the month there is an extra space, compare:

Nov  9 01:02:03 x.x.x.x
Nov 10 01:02:03 x.x.x.x

However, what you want is "three words before the IP", not "three (or four) spaces before the IP". Try something like this untested extraction:

^(?:[^\s]+\s+){3}(?P<FIELDNAME>(\d{1,3}\.){3}\d{1,3})

This looks for "positive number of non-spaces followed by positive number of spaces" (read: "words") three times, then picks out the IP while taking the decimal notation into account. Note, this would allow invalid IPs such as "999.999.999.999".

0 Karma
Get Updates on the Splunk Community!

The OpenTelemetry Certified Associate (OTCA) Exam

What’s this OTCA exam? The Linux Foundation offers the OpenTelemetry Certified Associate (OTCA) credential to ...

From Manual to Agentic: Level Up Your SOC at Cisco Live

Welcome to the Era of the Agentic SOC   Are you tired of being a manual alert responder? The security ...

Splunk Classroom Chronicles: Training Tales and Testimonials (Episode 4)

Welcome back to Splunk Classroom Chronicles, our ongoing series where we shine a light on what really happens ...