Splunk Search

Cannot use earliest and latest for _time field newly converted from other field ?

sieutruc
Contributor

Hello,

When i trigger a search like:

host="win20_oslo-ifs_CC-DC" index="sqlobj" | multikv | eval BusinessEpoch=strptime(BusinessDay,"%m/%d/%Y %I:%M:%S %p") | eval _time=BusinessEpoch  | table _time

It gives a table of _time field that is converted from BusinessDay, but if i use:

host="win20_oslo-ifs_CC-DC" index="sqlobj" | multikv | eval BusinessEpoch=strptime(BusinessDay,"%m/%d/%Y %I:%M:%S %p") | eval _time=BusinessEpoch  | search earliest=-1d latest=now | table _time

I've got no result , and i tried several times by changing the value of earliest or lastest but couldn't be successful. Can you suggest me what to do ?

Tags (3)
0 Karma
1 Solution

sideview
SplunkTrust
SplunkTrust

The earliest and latest searchterms will only function in the search command when it's the initial search command in the pipeline. This is because those searchterms are really just a shorthand way to submit the "earliest" and "latest" arguments to the Splunk search API, back when the search is being dispatched initially.

So to filter by time further down in the search pipeline, I would use the "relative_time" function that's available in the eval and where commands.

Specifically :

| where _time>=relative_time(now(),"-1h") AND _time<now()

View solution in original post

sideview
SplunkTrust
SplunkTrust

The earliest and latest searchterms will only function in the search command when it's the initial search command in the pipeline. This is because those searchterms are really just a shorthand way to submit the "earliest" and "latest" arguments to the Splunk search API, back when the search is being dispatched initially.

So to filter by time further down in the search pipeline, I would use the "relative_time" function that's available in the eval and where commands.

Specifically :

| where _time>=relative_time(now(),"-1h") AND _time<now()

vbumgarner
Contributor

So... side question...

Is there any way to "reset" the "search timeframe" so that all the "commands that bin" will honor a new "search timeframe" instead of the timeframe used in the original query?

0 Karma

sieutruc
Contributor

Thanks, yes i did one of both separately, but got no success too

0 Karma

Ayn
Legend

Did you try without "lastest"? Because that's a typo - it should be "latest"...

0 Karma
Get Updates on the Splunk Community!

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...

Splunk APM: New Product Features + Community Office Hours Recap!

Howdy Splunk Community! Over the past few months, we’ve had a lot going on in the world of Splunk Application ...