Security

Help on Correlation search scheduling

ajmach343
Explorer

Hello,

I am currently building correlation searches in ES and I am running into a "searches delayed" issue. some of my searches run every hour, most are every 2 hours, and some every 3, 12 hours.

My time range looks like:

Earliest Time: -2h 
Latest Time: now

cron schedule: 1 */2 * * *

for each new search I add +1 to the minute tab of the cron schedule up to 59 and then start over. 
so on the next search the schedule would be 2 */2 * * * and so on...

is there a more efficient way I should be scheduling searches?

Thank you.

Tags (1)
0 Karma

marnall
Motivator

No that should be fine. As long as you have enough CPU and threads and your correlation searches are not overlapping with its next execution (e.g. if the search runs every 2 hours but it takes 2.5 hours to complete), then you use the +1 minute technique to spread the searches around, then it should be fine.

Do you get warnings about concurrent searches or do you see high CPU usage in your monitoring console?

0 Karma

ajmach343
Explorer

I have about 800 searches. some that run take more than a minute. 

so in the messages it states: status: skipped, reason: "The maximum number of concurrent auto-summarization searches on this instance has been reached. " 

no warnings or errors. all messages have "INFO" right after date/time

cpu usage is at about 12% and memory usage is at 28%

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...