Splunk Search

Relative_time() and convert() Function

vasanthmss
Motivator

Hi Splunkers,

when i'm running first Search returns getting zero value where as second Search giving correct value. Explain me how its working,

Search 1:

|stats count | eval next_time=relative_time(now(),"-45y")

Search 2:

|stats count | eval next_time=relative_time(now(),"-45y")| convert ctime(*_time)
V
1 Solution

vasanthmss
Motivator

fdi01
Motivator

so see your command eval = next_time relative_time (now (), "- 45y") will provide no results that eventually you converted,
because if you run these commands get the same result
|stats count | eval next_time=relative_time(now(),"-45y")| convert ctime(_time)

or |stats count | convert ctime(
_time)

try the following different commands to understand the operation.
|stats count | convert ctime(count)
or
|stats count | convert timeformat="%H:%M:%S" ctime(count)
or
|stats count | eval next_time=count| convert ctime(_time) or |stats count | convert ctime(_time) next_time

0 Karma

kml_uvce
Builder

In first search its zero as its epoch time (start time) and when you are converting this epoch time in second search then its giving in date format
http://en.wikipedia.org/wiki/Unix_time

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...