Splunk Search

Alerts that go on waiting status causes next alerts to not trigger?

damucka
Builder

Hello,

We have several alerts which occasionally go in status waiting (correponding jobs) and stay like that. Then the next executions of these alerts are not triggered of course, so we get quite some skipped jobs.
The jobs overview states the jobs are in status "Parsing", however when I copy the corresponding search and execute in another search window it finishes quite fast. 
Please see also the screenshot  below. It seems to stuck in the following part (last entries in the search.log:
 
....
12-05-2022 06:40:02.915 INFO ChunkedExternProcessor [15318 searchOrchestrator]
- Running process: /vol1/opt/splunkdev2/splunk/bin/python3.7
/vol1/opt/splunkdev2/splunk/etc/apps/splunk_app_db_conn
 
damucka_0-1670321369947.png

 

 
I increased all possible limits and quotas I could come up with to lift any restrictions on the concurrency, but it did not help ...
 
How would I investigate it further?
 
Labels (1)
0 Karma
Get Updates on the Splunk Community!

Upcoming Webinar: Unmasking Insider Threats with Slunk Enterprise Security’s UEBA

Join us on Wed, Dec 10. at 10AM PST / 1PM EST for a live webinar and demo with Splunk experts! Discover how ...

.conf25 technical session recap of Observability for Gen AI: Monitoring LLM ...

If you’re unfamiliar, .conf is Splunk’s premier event where the Splunk community, customers, partners, and ...

A Season of Skills: New Splunk Courses to Light Up Your Learning Journey

There’s something special about this time of year—maybe it’s the glow of the holidays, maybe it’s the ...