Getting Data In

wrong event timestamp

SplunkCSIT
Communicator

After the data is forwarded to indexer, the date format for event seems to be incorrect for some events (whereby the day and month is less than 12) and correct for the rest (the day is more than 12), how come and what will be the remedy? The event timestamp is taken from the timestamp found inside the content of the data.

Correct timestamps:
02/03/2014
(dd/mm/yyyy)

14/03/2014
(dd/mm/yyyy)

incorrect timestamp:
02/03/2014
(mm/dd/yyyy)

Tags (1)
0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Specify a TIME_FORMAT in your props.conf to tell Splunk the order of month and day fields explicitly.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Do post your config so we can take a look.

0 Karma

SplunkCSIT
Communicator

also the same, it happened for only two dates, 1Mar and 2Mar, it recognise as 3Jan, 3Feb, the rest of the dates, it able to get the correct date format.

0 Karma

linu1988
Champion

you need to set props.conf in indexer not forwarder..

0 Karma

SplunkCSIT
Communicator

already set that in forwarder props.conf but date format for event seems to be incorrect for some events (whereby the day and month is less than 12) and correct for the rest (the day is more than 12). Any other suggestion?

0 Karma
Get Updates on the Splunk Community!

New Year. New Skills. New Course Releases from Splunk Education

A new year often inspires reflection—and reinvention. Whether your goals include strengthening your security ...

Splunk and TLS: It doesn't have to be too hard

Overview Creating a TLS cert for Splunk usage is pretty much standard openssl.  To make life better, use an ...

Faster Insights with AI, Streamlined Cloud-Native Operations, and More New Lantern ...

Splunk Lantern is a Splunk customer success center that provides practical guidance from Splunk experts on key ...