Splunk Search

Epoch timestamp extraction not working

Flynt
Splunk Employee
Splunk Employee

I'm having difficulty extracting an Epoch timestamp in the following format - 1361463359598

I can validate that this is a true Epoch time using many programs online. In my props.conf I have %s set which is supposed to give me the correct time of Thu, 21 Feb 2013 16:15:59 GMT.

However, splunkd.log keeps telling me this timestamp is invalid -

DateParserVerbose - The TIME_FORMAT specified is matching timestamps (Mon Jan 18 19:14:07 2038) outside of the acceptable time window.

Why is this happening and how can I tell Splunk to give me the correct timestamps?

Tags (3)
1 Solution

hexx
Splunk Employee
Splunk Employee

Your timestamp is expressed in milliseconds since the epoch, not seconds. This is why the %s TIME_FORMAT is not appropriate. Instead, use:

TIME_FORMAT = %s%3N

View solution in original post

hexx
Splunk Employee
Splunk Employee

Your timestamp is expressed in milliseconds since the epoch, not seconds. This is why the %s TIME_FORMAT is not appropriate. Instead, use:

TIME_FORMAT = %s%3N
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...