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
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...