Getting Data In

How to correct props.conf to resolve a timestamp mismatch?

joydeep741
Path Finder

For the log events which look like :-

PID-27654-(2016-06-12-08:00:02.677) [INFO] : Error Publisher Server

I have configured the props.conf as follows :-

[granite_server_forever]
SHOULD_LINEMERGE = false
TIME_FORMAT =%Y-%m-%d-%H:%M:%S.%3N
MAX_TIMESTAMP_LOOKAHEAD = 40
TIME_PREFIX = (

Do you see any error in the configurations ?
On the front end, we are facing issues because of timestamp mismatch.

On the search Head it looks like :

11/29/16
7:55:21.000 AM PID-1723-(2016-11-29-12:55:21.810) [INFO] : -a712fb49-0b04-4370-995a-c

Tags (2)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi joydeep741,
try modifying MAX_TIMESTAMP_LOOKAHEAD = 23 and adding TZ=your_time_zone

Bye.
Giuseppe

View solution in original post

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi joydeep741,
try modifying MAX_TIMESTAMP_LOOKAHEAD = 23 and adding TZ=your_time_zone

Bye.
Giuseppe

0 Karma

richgalloway
SplunkTrust
SplunkTrust

Try adding a TZ= attribute with the correct time zone setting to your props.conf.

---
If this reply helps you, Karma would be appreciated.
0 Karma
Get Updates on the Splunk Community!

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...

Splunk APM: New Product Features + Community Office Hours Recap!

Howdy Splunk Community! Over the past few months, we’ve had a lot going on in the world of Splunk Application ...

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...