Getting Data In

Unable to capture correct timestamp?

remy06
Contributor

hi,

I'm trying to configure splunk to display the time based on the event.

The event's timestamp format is something like this:
EXTENDED_TIMESTAMP="04-AUG-10 12.10.43.720287 AM +08:00"

I've configured props.conf with this:
[myevent]
TIME_PREFIX = EXTENDED_TIMESTAMP="
TIME_FORMAT = %d-%b-%y %I.%M.%S.%q %p
SHOULD_LINEMERGE = true

However,splunk occasionally display the wrong time as it translate AM as PM which is wrong.

Is there anything wrong with the config?

Tags (3)
0 Karma
1 Solution

stephanbuys
Path Finder

Hi Remy06,

Please try TIME_FORMAT = %d-%b-%y %I.%M.%S.%6N %p

I think it might be the difference between nano and milliseconds that's tripping it up.

For more detail check http://www.splunk.com/base/Documentation/4.1.4/admin/Configuretimestamprecognition

View solution in original post

remy06
Contributor

Hi,

Seems to have problems with it now.It's been working fine for the past few days..

Sample of the event: ......,EXTENDED_TIMESTAMP="20/08/10 12:59:21.994681 AM +08:00"....

props.conf
[myevent]
TIME_PREFIX = EXTENDED_TIMESTAMP="
TIME_FORMAT = %d/%m/%y %I:%M:%S.%6N %p
SHOULD_LINEMERGE = true

This morning I've noticed the dates are specified in splunk as:
10/12/08
12:59:21.994 AM

Any idea?

0 Karma

stephanbuys
Path Finder

Hi Remy06,

Please try TIME_FORMAT = %d-%b-%y %I.%M.%S.%6N %p

I think it might be the difference between nano and milliseconds that's tripping it up.

For more detail check http://www.splunk.com/base/Documentation/4.1.4/admin/Configuretimestamprecognition

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...