Getting Data In

Event and log timestamps are off by a bit

sprimerib
New Member

Local splunk server timezone is GMT. Incoming firewall logs are in Eastern. But when I query, the times are off when comparing the Time and Event columns.

(can't add screen shot because of "points"):

Time column:
6/19/18 11:02:33.000 PM

Event column:
Jun 19 18:02:33 192.168.100.1 Jun 19 2018 14:02:33

Local time for me is 2:02 PM.

What is the best way to resolve this?

Tags (2)
0 Karma

solarboyz1
Builder

It appears your events have two timestamps:

Jun 19 18:02:33 192.168.100.1 Jun 19 2018 14:02:33

I normally see this when syslog receives and adds a timestamp to the events received remotely.

Assuming the 14:02 timestamp is EST, then it appears the first timestamp is MST (EST + 2)
Splunk always attempts to offset the time to GMT.

My guess is that Splunk is applying an offset at index time, in an attempt to make the time GMT.
Then its offsetting again at search time, based on your TZ preference.

It appears you need to fix your props to apply the correct TZ for this source, or extract the correct timestamp.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...