Getting Data In

Timestamp format

merp96
Path Finder

What could be the TIME_FORMAT=? for the below timestamp in event
2015-03-18 14:18:17 0.175

0 Karma
1 Solution

inventsekar
SplunkTrust
SplunkTrust

2015-03-18 14:18:17 0.175 --- may i know what is this 0. before 175(milli seconds)

please try this in props.conf:

 TIME_FORMAT = %Y-%d-%m %H:%M:%S

Best Regards,
Sekar

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !

View solution in original post

inventsekar
SplunkTrust
SplunkTrust

2015-03-18 14:18:17 0.175 --- may i know what is this 0. before 175(milli seconds)

please try this in props.conf:

 TIME_FORMAT = %Y-%d-%m %H:%M:%S

Best Regards,
Sekar

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !

merp96
Path Finder

I guess 0.175 is not part of timestamp. What do you think about it.

0 Karma

inventsekar
SplunkTrust
SplunkTrust

ok then, we can discard it. use only till %S
TIME_FORMAT = %Y-%d-%m %H:%M:%S

if "0." was not there, then, we can think of it as 175 milli seconds (%N).
may be its part of the remaining line.

thanks and best regards,
Sekar

PS - If this or any post helped you in any way, pls consider upvoting, thanks for reading !
0 Karma

merp96
Path Finder

yes I believe so, will check with the team logging the source
Thanks

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...