For example, 637 in second to 0:10:37 in the exported search result.
| eval field_in_hhmmss=tostring(field_in_secs, "duration")
field_in_hhmmss
is the newly formatted field
field_in_secs
is the field name whose values are in seconds
| eval field_in_hhmmss=tostring(field_in_secs, "duration")
field_in_hhmmss
is the newly formatted field
field_in_secs
is the field name whose values are in seconds
Thanks for the updated answer. I forget when we introduced this, but it was probably before 5.x.
https://github.com/RubenOlsen/splunkcommands/tree/master/sec2time
working awesome
i strongly recommend this
We have some conversion functions for converting an offset in seconds from the UNIX epoch to a human-readable datetime, such as from 1266394237 to Jan 3, 2009, 02:13:45 PST.
For your case of a duration in seconds to a human readable duration, we do not have any built-in facility in 4.0. In 4.1, the method will be |eval pretty_time=tostring(num_seconds, "duration") where num_seconds is an integer quantity of seconds or a decimal quantity of seconds and sub-seconds. This should get documented in Functions for Eval and Where. It will emit HH:MM:SS or DD+HH:MM:SS if over a day
See also SPL-25013
My simplistic method for 3.x which should also work in 4.0 was:splunk> search terms... |eval my_hours=seconds / 60 / 60| eval my_minutes = seconds / 60 - my_hours * 60 | eval my_seconds = seconds - my_hours * 60 * 60 - my_minutes * 60 | strcat my_hours ":" my_minutes ":" my_seconds my_time
This created a field called my_time with the string version.
I have created a custom search command which correctly returns
Take a look at https://github.com/RubenOlsen/splunkcommands/tree/master/sec2time
Use http://www.epochconverter.com/ or such to find some epoch time for a midnight. Say, 1266393600 is "Wed 17 Feb 2010 12:00:00 AM PST". Now, add your input of 637, getting 1266394237.
splunk search "* | head 1 | eval foo=1266394237 | convert timeformat=%H:%M:%S ctime(foo) | fields foo | fields - _*" -auth admin:changeme -preview 0
gives
foo
--------
00:10:37
Yes it's ugly, but it works! 😉
To extract from a multivalue field, please see explanation here: http://answers.splunk.com/questions/285. Does that work for you, Splunker_J?
Thanks! In this case, foo is not a specific value, it is a field with many value in splunk's search results.