Splunk Search

'earliest': '03/09/2019:17:07:00' is significantly slower than "earliest_time": "-2d" (earliest vs. earliest_time)

coreybfoulds
New Member

Greetings,

'earliest': '03/09/2019:17:07:00' is significantly slower than "earliest_time": "-2d". Is this a known issue? If so, is there a reason for this?

0 Karma

chrisyounger
SplunkTrust
SplunkTrust

"earliest" is not special value for either the REST API or normal search. As such, what happens when you do a search with that is that it will look for any records that have that exact key and that exact value. If you are on an older version of Splunk, the default will be "all time" and it will be very slow.

If you are using the REST API? The documentation here lists the valid keys:

https://docs.splunk.com/Documentation/Splunk/7.2.4/RESTREF/RESTsearch#search.2Fjobs

(expand [POST])

All the best

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

Got a little more context?

Also, what value do you see in the job inspector for earliestTime and latestTime?

0 Karma
Get Updates on the Splunk Community!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.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 ...