Splunk Search

Time modifiers for Search and Time zones

spiketide
Engager

Hi All,

The timezone in my splunk setup is IST (UTC + 5.30)

From the examples at
http://docs.splunk.com/Documentation/Splunk/5.0.3/Search/Specifytimemodifiersinyoursearch

if the current time is Jul 4, 2013 8:11:56.000 PM

Then -1h@h = Jul 4, 2013 7:00:00.000 PM

But in my setup, when the current time is

Jul 4, 2013 8:11:56.000 PM

-1h@h returns Jul 4, 2013 6:30:00.000 PM

Taking into account the conversion of time between UTC and IST, is this behavior correct?

0 Karma

gkanapathy
Splunk Employee
Splunk Employee

Well, the definition of the @h "snap-to" times is not specified whether it's snapped to UTC or to local time. But I would expect that it would snap to local time, to be consistent with @d and @m snap-to times.. I would open a case with Splunk support about this, as it's probably an oversight. What may be worse is that snap-to @d or @m may also snap to incorrect times, which would clearly be a bug.

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