Getting Data In

How to get Splunk to recognize correct event timestamp from extracted log?

newbiesplunk
Path Finder

Hi,
When i inject app server logs with sourcetype=access_combined, the timing for the event timestamp seems to be incorrect. The date timestamp is correct but the timing timestamp, it tag the timing as stated in the info after the GET statement.

Extracted info from the logs:
xxxxx - 1234 [07/Aug/2014:07:15:01 _0800] "Get xxxxx/20140807141314...." 200 123 ....

AT splunk, the event timestamp is:
8/7/14
14:13:14 PM xxxxx - 1234 [07/Aug/2014:07:15:01 _0800] "Get xxxxx/20140807141314...." 200 123 ....

Would like to check how to ensure the event timestamp is the timestamp as stated in the square bracket instead of the timing found in the GET statement? What had configured for this incorrect timestamp?
thks

Tags (1)
0 Karma

strive
Influencer

I think you need to override the default options of [access_combined]

Try this

Add the below stanza to your /local/props.conf

[access_combined]  
MAX_TIMESTAMP_LOOKAHEAD = 50  
TIME_PREFIX = \[  
TIME_FORMAT = %d/%b/%Y:%H:%M:%S %z
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...