Getting Data In

Time Zone Confusion

tgiles
Path Finder

Hi, All.

I’m running into an issue with heavy forwarders not setting the time zone correctly when sending logs to my indexer. All indexers are on CST, and forwarders can be pretty much anything.

I’ll step through a device and see if you can pin down where I’m doing it terribly wrong. The available docs aren't the most clear-cut on this topic.

OK, log in to a system with a date problem, check the date:

SWEB1 ~ # date
Mon Jul 23 18:21:03 EDT 2012

edit /opt/splunk/etc/system/local/props.conf on the heavy forwarder and set the time zone:

[host::*]
TZ = US/Eastern

Restart the heavy forwarder, view logs on indexer. They’re still showing up with the incorrect time zone (I.E. one hour off from CST)

What do I need to do to make the EST logs on the heavy forwarder show up as CST on the indexer?

According to the docs, the examples like US/Eastern and US/ Pacific are used as for setting Splunk TZ, then points us to Wikipedia for a much more thorough treatment of what to put in there.

However, the Wikipedia page does not use either US/Eastern and US/ Pacific at all for TZ entries. America/New_York or America/Los_Angeles is listed as correct. Which one will work best for Splunk?

Edit: this is occurring with all new data sent by the forwarder after I adjusted the props.conf on the heavy forwarder. I'm ignoring any historical data for this test.

If you could point me in the right direction, I'd appreciate it.

tom

Tags (1)

lguinn2
Legend

So here's the deal - the timezone setting will only apply to new data arriving in Splunk. Any existing data (that has already been indexed) will not be changed.

So the only way to correct the data would be to remove it from the index and then reindex it. This will be a tedious endeavor, but it may be your best solution.

Here is a pretty good entry that describes the steps in reindexing.

tgiles
Path Finder

Hi, Thanks for the input. I probably should have been clearer- all of the new data coming into the indexer is still an hour off, even after performing a timezone adjustment on the forwarder.

0 Karma
Get Updates on the Splunk Community!

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...

Purpose in Action: How Splunk Is Helping Power an Inclusive Future for All

At Cisco, purpose isn’t a tagline—it’s a commitment. Cisco’s FY25 Purpose Report outlines how the company is ...

[Upcoming Webinar] Demo Day: Transforming IT Operations with Splunk

Join us for a live Demo Day at the Cisco Store on January 21st 10:00am - 11:00am PST In the fast-paced world ...