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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

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

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...