Splunk Search

How to set lower and upper threshold deviation?

majilan1
Path Finder

Hi Splunkers,

This may be easy, but I'm not able to solve it if anyone can help.

I want to set a lower threshold to 15 standard deviation below the mean, and the upper threshold to 15 standard deviation above the mean, but I'm not sure how to implement that. 

Thanks!

0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

The general idea is to use the eventstats command to compute the standard deviation then use eval to calculate the lower and upper thresholds.  Like this:

| eventstats stdev(foo) as stdev, avg(foo) as avg
| eval lower=avg - stdev*15, upper=avg+stdev*15
| where (foo < lower OR foo > upper)

 

---
If this reply helps you, Karma would be appreciated.

View solution in original post

0 Karma

majilan1
Path Finder

How would I implement that in what I do have, please? So this is what I have:

index=X  sourcetype=Y source=metrics.kv_log appln_name IN ("FEED_FILE_ROUTE", "FEED_INGEST_ROUTE") this_hour="*"

| bin span=1h _time

| stats latest(this-hour) AS Volume BY appln_name, _time

| eval day_of_week=strftime(_time,"%A"), hour=strftime(_time,"%H")

|lookup mt_expected_processed_volume.csv name as appln_name, day_of_week, hour

outputnew avg_volume, stdev_volume

0 Karma

richgalloway
SplunkTrust
SplunkTrust

The general idea is to use the eventstats command to compute the standard deviation then use eval to calculate the lower and upper thresholds.  Like this:

| eventstats stdev(foo) as stdev, avg(foo) as avg
| eval lower=avg - stdev*15, upper=avg+stdev*15
| where (foo < lower OR foo > upper)

 

---
If this reply helps you, Karma would be appreciated.
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 ...