Getting Data In

Properly Extract Time from custom Data Set

hagjos43
Contributor

Hello, I have the follow data set comprised of custom weblog output:

2015-08-08 12:40:03:163 UserID="37" userGroup="helloworld1192" userRole="test82" commonName="insertnamehereagainandagain" certName="HENRY.T.WASHINGTON" ipAddress="192.168.1.83" userBrowser="Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko"

I have the following in my Props.conf on the indexer:

[customwebtest]
LINE_BREAKER = (\d{4}\S\d{2}\S\d{2}\s\d{2}\S\d{2}\S\d{2}\S\d{3})
SHOULD_LINEMERGE = false
CHECK_FOR_HEADER = false
MAX_TIMESTAMP_LOOKAHEAD = 23
TIME_PREFIX = ^
TIME_FORMAT = (%y-%m-%d %H:%M:%S:%3N)

Problem is in Splunk it's excluding the event timestamp and using the time at ingestion. What am I doing wrong here?

Thanks!

0 Karma
1 Solution

schose
Builder

Remove your LINE_BREAKER and you should be fine.

Cheers,

Andreas

View solution in original post

schose
Builder

Remove your LINE_BREAKER and you should be fine.

Cheers,

Andreas

richgalloway
SplunkTrust
SplunkTrust

The value of the LINE_BREAKER attribute is the event separator - characters that come between events. Whatever matches the first capturing group is discarded. If your log has one event per line then the default LINE_BREAKER=\n should be sufficient.

---
If this reply helps you, Karma would be appreciated.
0 Karma

pradeepkumarg
Influencer

Your time format is wrong. It should be uppercase Y for the year if it includes centuary

 TIME_FORMAT = %Y-%m-%d %H:%M:%S:%3N

http://docs.splunk.com/Documentation/Splunk/6.2.5/SearchReference/Commontimeformatvariables

0 Karma
Get Updates on the Splunk Community!

AI for AppInspect

We’re excited to announce two new updates to AppInspect designed to save you time and make the app approval ...

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...