Splunk Search

Props.conf and LINE_BREAKER Regex

Drainy
Champion

I have created a regex;

(\d+)(:)(\d+)(:)(\d+)(\.)(\d+)

To act as my LINE_BREAKER in the props conf file for an app I am currently working on.
The log data is generated by a script and the length of each event output by the script is variable in length and contents however the first entry is always a timestamp of the format;

13:36:18.680336

In the documentation is the following paragraph;

  • Wherever the regex matches, Splunk considers the start of the first matching group to be the end of the previous event, and considers the end of the first matching group to be the start of the next event.

From http://www.splunk.com/base/Documentation/Latest/Admin/Propsconf

Now I understand that as meaning that it will interpret my regex, when a match is made it will move to the end of the matched data and count that as the beginning of my event.
Thats not ideal as I really want to keep all the event data, but as a test I tried it and instead it caught all of my event but missed the first two integers of my timestamp like so;

:36:18.680336

I assume its my regex or understanding/implementation thats at fault? Any ideas would be appreciated.

Tags (2)
1 Solution

dwaddle
SplunkTrust
SplunkTrust

LINE_BREAKER gobbles the first capture group. You might try this:

([\r\n]+)(\d+)(:)(\d+)(:)(\d+)(\.)(\d+)

View solution in original post

dwaddle
SplunkTrust
SplunkTrust

LINE_BREAKER gobbles the first capture group. You might try this:

([\r\n]+)(\d+)(:)(\d+)(:)(\d+)(\.)(\d+)
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!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...