Splunk Search

anomalousvalue misuse or bug?

steve
Path Finder

I ran the following:

source="/path/to/vpn_log" | anomalousvalue action=summary date_hour

Every event was normal (even after changing pthresh). I noticed the mean and stddev were all 0. The IsNum column is Yes as exepcted, but the UseNum column is No which seems odd.

Am I using this incorrectly (or expecting the wrong results)? Running 5.0.1. I didn't see any known bugs or see this in the changelog for 5.0.2.

Tags (1)
0 Karma
1 Solution

steve
Path Finder

Found the issue. You have to have 100 or more events in the search before the mean and standard deviation will be calculated.

View solution in original post

0 Karma

steve
Path Finder

Found the issue. You have to have 100 or more events in the search before the mean and standard deviation will be calculated.

0 Karma
Get Updates on the Splunk Community!

Announcing the Expansion of the Splunk Academic Alliance Program

The Splunk Community is more than just an online forum — it’s a network of passionate users, administrators, ...

Learn Splunk Insider Insights, Do More With Gen AI, & Find 20+ New Use Cases You Can ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Buttercup Games: Further Dashboarding Techniques (Part 7)

This series of blogs assumes you have already completed the Splunk Enterprise Search Tutorial as it uses the ...