Are you a member of the Splunk Community?
- Find Answers
- :
- Using Splunk
- :
- Other Using Splunk
- :
- Alerting
- :
- Is there a limitation related to the number of rea...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have two servers Splunk Enterprise that collected the same inputs mainly in syslog. I have created some real-time alerts to prevent us when some events occured in our network. I have declared more than ten real-time alerts but only five or six alerts worked.
The others alerts never triggered.
Do you know if there is a limitation with a license or technical constraint in Splunk Enterprise?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it's technically constrained somewhat by the number of CPU cores available on your search head. Generally it's better to use scheduled searches on 5 minute (or 1 minute if you really need it that fast) intervals. Once you hit the concurrent search limit (because there aren't any cores left to run the searches), the search head will start queuing ad-hoc search jobs and skipping scheduled searches.
Related question: https://answers.splunk.com/answers/92760/impact-of-real-time-distributed-searches-on-cpu-utilization...
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is the rolling-windows alerts are considered as real-time alerts?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, it's technically constrained somewhat by the number of CPU cores available on your search head. Generally it's better to use scheduled searches on 5 minute (or 1 minute if you really need it that fast) intervals. Once you hit the concurrent search limit (because there aren't any cores left to run the searches), the search head will start queuing ad-hoc search jobs and skipping scheduled searches.
Related question: https://answers.splunk.com/answers/92760/impact-of-real-time-distributed-searches-on-cpu-utilization...
Level Up Your .conf25: Splunk Arcade Comes to Boston
Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...
Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform
