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
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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...