Splunk Search

saved searches accessing the same index at the same time

drussell88
Explorer

I have a lot of saved searches that are scheduled to search the same index at the same time. What is an good number of searches I can run like this efficiently? I have an issue with my average execution lag time increasing over time. I have to restart my search head to alleviate the problem.

Tags (1)
0 Karma

aimeeanne
New Member

spam removed

0 Karma

aimeeanne
New Member

spam removed

0 Karma

aimeeanne
New Member

spam removed

0 Karma

lguinn2
Legend

How many cores do you have on your search head? That is approximately the number of searches that Splunk can run simultaneously. If you have more than that scheduled, then some searches will wait. Also, you must include the count of ad-hoc searches that logged-in users are running in your total number of searches.

Does your search head meet the recommended size?

Do you have enough indexers? Are the indexers the recommended size?

To make searches go faster, your best investment is almost always to add another indexer. In a large environment, some people have a search head that runs nothing but scheduled searches - this is called a job server - and it prevents logged-in users from impacting the scheduled searches and vice-versa.

But these are just general comments. You really need to do more analysis of what's happening in your environment.
Here are some links:

Hardware capacity planning

Summary of Performance Recommendations

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