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