Splunk Search

time difference issue

changwoo
Communicator

start_time = > 2014-02-13T22:57:15+0900

end_ time = > 2014-02-13T23:59:54+0900

how can i get the time difference ??

i tried

convert timeformat="%Y/%m/%d %H:%M:%S" mktime(start_time) AS StartTime_epoch mktime(end_time) AS ResolvedTime_epoch | eval total=round((ResolvedTime_epoch-StartTime_epoch)/60/60/24)

Tags (2)
0 Karma
1 Solution

kristian_kolb
Ultra Champion

Try this,

your_base_search 
| eval epoch_st = strptime(start_time, "%Y-%m-%dT%H:%M:%S%z") 
| eval epoch_et = strptime(end_time, "%Y-%m-%dT%H:%M:%S%z")
| eval epoch_diff = epoch_et - epoch_st
| eval dur=tostring(epoch_diff, "duration")

http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/CommonEvalFunctions

/K

View solution in original post

kristian_kolb
Ultra Champion

Try this,

your_base_search 
| eval epoch_st = strptime(start_time, "%Y-%m-%dT%H:%M:%S%z") 
| eval epoch_et = strptime(end_time, "%Y-%m-%dT%H:%M:%S%z")
| eval epoch_diff = epoch_et - epoch_st
| eval dur=tostring(epoch_diff, "duration")

http://docs.splunk.com/Documentation/Splunk/latest/SearchReference/CommonEvalFunctions

/K

kristian_kolb
Ultra Champion

oh well, if your fields are actually called start_time and end_time, the new fields should come out fine. However, they do not show in the event text (_raw), but you can use them in tables, charts, stats etc.

0 Karma

changwoo
Communicator

i tried but epoch_st epoch_et, epoch_diff , dur field is not comming out ..

it's showing the _raw data...

0 Karma
Get Updates on the Splunk Community!

Splunk Decoded: Service Maps vs Service Analyzer Tree View vs Flow Maps

It’s Monday morning, and your phone is buzzing with alert escalations – your customer-facing portal is running ...

What’s New in Splunk Observability – September 2025

What's NewWe are excited to announce the latest enhancements to Splunk Observability, designed to help ITOps ...

Fun with Regular Expression - multiples of nine

Fun with Regular Expression - multiples of nineThis challenge was first posted on Slack #regex channel ...