Developing for Splunk Enterprise
Highlighted

earliest_time in POST call versus earliest in query itself

Path Finder

I am sending a POST call to the REST endpoint search/jobs with following parameters:

    'output_mode': 'json',
    'earliest_time': '-7d',
    'latest_time': '-1d',
    'exec_mode': 'oneshot',
    'search': 'search index=ind status=FAIL | table error, sim_time'

If, instead of above, I send:

    'output_mode': 'json',
    'exec_mode': 'oneshot',
    'search': 'search index=ind earliest=-7d@d latest=-1d@d status=FAIL | table error, sim_time'

Is there a difference? In terms of performance, load on server, correctness etc.

0 Karma
Highlighted

Re: earliest_time in POST call versus earliest in query itself

SplunkTrust
SplunkTrust

Aside from the fact that you're snapping to the day in one search and not the other, there should be no difference in performance.

View solution in original post

0 Karma
Highlighted

Re: earliest_time in POST call versus earliest in query itself

Path Finder

Sorry, I missed the @d in one search! Both searches are supposed to be the same. No difference sounds great!

0 Karma
Highlighted

Re: earliest_time in POST call versus earliest in query itself

SplunkTrust
SplunkTrust

You can always test both 10-20 times and avaerage the results. The _internal index has data related to how long the searches took.

0 Karma