Reporting

Why is scheduled job taking so long?

matstap
Communicator

I have a scheduled saved search that just calls a dbxoutput. When I run it manually, it finishes in a few minutes. When I schedule it to run, however, it takes 6 hours.

What logs/places should I check to try to find out why this is happening?

0 Karma
1 Solution

PowerPacked
Builder

Hi @matstap

You can find info about scheduled searches in

index=_internal sourcetype=scheduler savedsearch_name=yoursearchname

look at things like scheduledtime,dispatch time, run time, status

Thanks

View solution in original post

PowerPacked
Builder

Hi @matstap

You can find info about scheduled searches in

index=_internal sourcetype=scheduler savedsearch_name=yoursearchname

look at things like scheduledtime,dispatch time, run time, status

Thanks

the_wolverine
Champion

Check to see whether you've supplied a timerange in the scheduled search. This a common mistake -- missing timerange. Without a timerange Splunk attempts to run the search across "All Time".

0 Karma
Get Updates on the Splunk Community!

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

Index This | Forward, I’m heavy; backward, I’m not. What am I?

April 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

A Guide To Cloud Migration Success

As enterprises’ rapid expansion to the cloud continues, IT leaders are continuously looking for ways to focus ...