Getting Data In

Is it better to specify TIME_FORMAT or let Splunk automatically determine time format?

bolaojewale
Explorer

Hey,
I am currently doing clean up work on some of the in house TA's build for our environment. We are getting timestamps in a more consistent way on some sources and I was wondering what would improve indexer performance? We previously had the following time-related settings in our props.conf

TIME_PREFIX = ^
TIME_FORMAT = %Y-%m-%d %H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD = 20

I want to remove the TIME_PREFIX and TIME_FORMAT settings and just leave MAX_TIMESTAMP_LOOKAHEAD.

Does this even matter?

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

Always specify TIME_FORMAT, TIME_PREFIX, and MAX_TIMESTAMP_LOOKAHEAD. Without them, Splunk has to guess at where the timestamp is in your events. This impedes performance. If you want to clean up your TAs, add these attributes for the sourcetypes that are lacking them.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

Always specify TIME_FORMAT, TIME_PREFIX, and MAX_TIMESTAMP_LOOKAHEAD. Without them, Splunk has to guess at where the timestamp is in your events. This impedes performance. If you want to clean up your TAs, add these attributes for the sourcetypes that are lacking them.

---
If this reply helps you, Karma would be appreciated.
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 ...