Getting Data In

Setting timezone is not working

strive
Influencer

Hi,

We are using Splunk 6.0.3

The host (no matter where it is located) always sends logs with UTC time. In my props.conf file i have added TZ = UTC in the stanza that processes the logs. But still i see the _time as forwarder's time zone.alt text

My Props.conf looks like this:

SHOULD_LINEMERGE=false

LINE_BREAKER=([\r\n]+)\d{2}-[a-zA-Z]{3}-\d{4}\s\d{2}:\d{2}:\d{2}\s

MAX_TIMESTAMP_LOOKAHEAD=20

TIME_PREFIX=^

TIME_FORMAT=%d-%b-%Y %H:%M:%S

TZ=UTC

Thanks

Strive

Tags (1)
1 Solution

lukejadamec
Super Champion

Splunk will set event time zones according to the following priority:

1) It will use the time zone in the raw event data.

2) It will use the time zone in props.conf

3) If both the forwarder and indexer are 6.0 or later, then it used the time zone of the forwarder.

In your case, the time zone of the event is UTC because the time zone is included in the event.

However, because your MAX_TIMESTAMP_LOOKAHEAD is set to 20, Splunk never sees the time zone so it can't apply it.

I’m not sure why it does not check props.conf before it moves on to the third priority. Perhaps the props.conf is in the wrong location?

Regardless, change your MAX_TIMESTAMP_LOOKAHEAD to 30.

View solution in original post

0 Karma

lukejadamec
Super Champion

Splunk will set event time zones according to the following priority:

1) It will use the time zone in the raw event data.

2) It will use the time zone in props.conf

3) If both the forwarder and indexer are 6.0 or later, then it used the time zone of the forwarder.

In your case, the time zone of the event is UTC because the time zone is included in the event.

However, because your MAX_TIMESTAMP_LOOKAHEAD is set to 20, Splunk never sees the time zone so it can't apply it.

I’m not sure why it does not check props.conf before it moves on to the third priority. Perhaps the props.conf is in the wrong location?

Regardless, change your MAX_TIMESTAMP_LOOKAHEAD to 30.

0 Karma

strive
Influencer

The issue was with forwarder. It is resolved.

jdhruti
New Member

what's was the issue? we are having the same issue where the timezone is set as UTC, but it still indexes data in EDT.

0 Karma

strive
Influencer

Thanks for your response. props.conf is inside /IndexAPP/local/ directory. This splunk app is added to peer nodes (indexers).

Note: we use clusters

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!

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...

Splunk Agent Observability: Measuring AI Value with Splunk Tokenomics on AWS

The AI landscape is moving faster than ever, and our latest 2026 State of Observability report provides the ...

Enterprise Security Watch Party: What’s New in 8.8 - Recap

Splunk Community HQ hosted a Splunk Enterprise Security Watch Party: What’s New In ES 8.8 last Thursday. I had ...