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!

Event Series: Level up your SOC: Advancing with Splunk Enterprise Security

AI has fundamentally raised the stakes for security operations, and this three-part series is your guide to ...

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 ...

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...