Alerting

Machine Learning Outliers in Enterprise Security

daniel_althoff8
Loves-to-Learn

I have set up some Numerical Outlier detections in the MLTK, on our ES Search Head. 

They are set up as alerts in Splunk on our Enterprise Security Search Head. 

The Numerical Outlier alert looks back over a 2 hour time range. Which creates 24 data points (120 mins / 5 min increments = 24 event data points) Screen Shot 2021-07-29 at 9.19.57 AM.png

 

The problem is - in Enterprise Security (since this is a notable event), we receive 24 separate notable events! We correctly only receive 1 email each time the alert fires, but 24 notable events in ES. 

I have the alert set to trigger "Once", rather than "Per Result"

 

Is there anything else I can do to make sure ES doesn't get slammed with 24 notables every time this alert fires? 

 

Screen Shot 2021-07-29 at 9.23.41 AM.png

Labels (2)
Tags (1)
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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...