Getting Data In

UTC timezone missing?

David_Hodgson
Engager

For clarity, the support staff work in UTC when looking at logs. The Splunk indexers are all running with /etc/localtime => UTC

The new versions seem to be ignoring the server timezone and using GMT instead.

I cannot see an option in the user administration timezone dropdown for UTC, or is this the wrong way to set the UI timezone?

p.s. this seems to be new behaviour. Has someone "corrected" the UI timezone handling?

Tags (2)
0 Karma

muebel
SplunkTrust
SplunkTrust

Hi David, The timezone database used by Splunk is usually taken from the OS it's running on, as described here : http://docs.splunk.com/Documentation/Splunk/6.4.3/Data/Applytimezoneoffsetstotimestamps

GMT should usually be the same as UTC, unless you are dealing with British Summer Time. For my instance of Splunk I am finding a GMT timezone option for my user, and also a GMT : London. I'm presuming the simple "GMT" designation is UTC.

Please let me know if this helps!

0 Karma

David_Hodgson
Engager

Unfortunately GMT is described as one of London, Dublin etc. That implies it's using summer time (BST), which for my case is wrong.

There seems to be no way, using the UI, to set a user to have unaltered times reported.

I've edited the user's user-props.conf to have tz = UTC, but it's a defect that this isn't available through the UI, and that setting the user to "Default System Timezone" isn't working.

0 Karma
Get Updates on the Splunk Community!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...