Getting Data In

Searching indexes with your timezone set differently to the data's timezone

mtmoore
Explorer

Our data's date field uses UTC for all data across the globe for this one set of data. This is fine.

When a user runs a search using earliest and latest, unless I am mistaken, the date/time field it uses will be the timestamp placed on the data by Splunk and not the date field that is in the logs.

This is all well and good if the 2 date/times match up - even then though the user can change their timezone and this goes out of whack.

How can I force the search to look at the last 7 days using the UTC date/time stamp within the log itself and not Splunk's date/time stamp?

Thanks!

Tags (1)
0 Karma

blebit
Path Finder

or you can edit from your server

props.conf

[host:: the_host]
TZ = Location_TimeZone

0 Karma

mtmoore
Explorer

How will this force a search to use the date time zone of the raw log as opposed to the Splunk date/time based on your personal timezone settings?

0 Karma

blebit
Path Finder

props.conf @ remote location

TZ=Location_TimeZone

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