Alerting

Alert Problem

mathiasy123
Path Finder

Why did I get a warning on my real-time rolling windows alert?

mathiasy123_1-1593514193244.png

this is my alert configuration:

mathiasy123_2-1593514230801.png

 

Labels (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust
The best solution is to not run real-time alerts. They're rarely the answer.
If you insist on running real-time alerts then you will have to increase the number of CPUs on your search heads and indexers to match the number of real-time searches you want to run.
---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

richgalloway
SplunkTrust
SplunkTrust
You're running too many real-time searches. Why are you running real-time searches at all? Each one ties up a CPU forever so you're severely limiting the number of searches Splunk can run. Real-time searches should be reserved for alerts that require a real-time response. The alert shown could easily be replaced by a scheduled search that runs every 10 minutes.
---
If this reply helps you, Karma would be appreciated.
0 Karma

mathiasy123
Path Finder

So, what is the best solution if I want to run real-time alert ?

0 Karma

richgalloway
SplunkTrust
SplunkTrust
The best solution is to not run real-time alerts. They're rarely the answer.
If you insist on running real-time alerts then you will have to increase the number of CPUs on your search heads and indexers to match the number of real-time searches you want to run.
---
If this reply helps you, Karma would be appreciated.
0 Karma

mathiasy123
Path Finder

Ah, I see, so 1 CPU process 1 real-time search alert?, I guess should try schedule alert, thx!

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...