topic Re: How to correct props.conf to resolve a timestamp mismatch? in Getting Data In

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

joydeep741 — Tue, 29 Sep 2020 11:56:54 GMT

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

richgalloway — Tue, 29 Nov 2016 13:30:08 GMT

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

gcusello — Tue, 29 Nov 2016 13:56:23 GMT

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

Bye.
Giuseppe