Splunk Search

Trouble with UTC time

BearMormont
Path Finder

I have some search results that return values in the format %Y-%m-%d %H:%M:%S. For example:

...some search... | table UpdateTime

This would yield the following table:

UpdateTime

2018-06-06 13:49:28
2017-12-22 08:23:21

I know for a fact that time string is in UTC, not my local time. All I need to do is display the number of minutes that have elapsed between that UTC string and the time the event was recorded (_time). Everything I try keeps giving me negative numbers for recent events, I assume because it is treating the UpdateTime field as being in local time, not UTC.

Can anyone help me?

Tags (2)
0 Karma
1 Solution

BearMormont
Path Finder

Figured it out. Update Time needed a timezone identifier:

eval UpdateTime = UpdateTime." UTC"

Then I can convert the value properly:

eval EpochTime = strptime(UpdateTime, "%Y-%m-%d %H:%M:%S %Z")
eval ElapsedMinutes = (_time - UpdateTime) / 60

View solution in original post

0 Karma

BearMormont
Path Finder

Figured it out. Update Time needed a timezone identifier:

eval UpdateTime = UpdateTime." UTC"

Then I can convert the value properly:

eval EpochTime = strptime(UpdateTime, "%Y-%m-%d %H:%M:%S %Z")
eval ElapsedMinutes = (_time - UpdateTime) / 60
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!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...