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!

New This Month in Splunk Observability Cloud - Metrics Usage Analytics, Enhanced K8s ...

The latest enhancements across the Splunk Observability portfolio deliver greater flexibility, better data and ...

Alerting Best Practices: How to Create Good Detectors

At their best, detectors and the alerts they trigger notify teams when applications aren’t performing as ...

Discover Powerful New Features in Splunk Cloud Platform: Enhanced Analytics, ...

Hey Splunky people! We are excited to share the latest updates in Splunk Cloud Platform 9.3.2408. In this ...