Assure1 Metric Abnormal Threshold Engine

Overview

The Assure1 Metric Abnormal Threshold Engine utilizes the Holt-Winters algorithm to given metrics to establish a range that a metric's value should remain within during normal operating conditions. The engine will trigger an Abnormal Threshold crossing violation when the metric values exceed the normal behavior range. Once started, the Abnormal Threshold engine adapts to long-term patterns within the metrics. This engine is often used to monitor metrics such as bandwidth. Additional information can be found at the following link: http://usenix.org/legacy/publications/library/proceedings/lisa2000/full_papers/brutlag/brutlag_html/index.html

Abnormal Threshold Engine Setup

Note

As part of using the Abnormal Threshold Engine application, the Metric Standard Thresholding Engine must also be enabled and running to process threshold violation messages into events.

1. Add Abnormal Profile(s) or modify existing Abnormal Profile(s):

   Configuration -> Metrics -> Thresholds -> Abnormal Profiles

2. Add Threshold(s) or modify existing Threshold(s):

   Configuration -> Metrics -> Thresholds -> Thresholds

   • Type must be: Abnormal

3. Add threshold(s) to metrics. This can be done in several ways:

   • This can be done manually on the Metrics UI: Configuration -> Metrics -> Metrics

   • Added during metric creation when using Polling Assignments or Polling Policies. See the related documentation:

     Configuration -> Metrics -> Polling Assignments

     Configuration -> Metrics -> Polling Policies

   • Added to the metric during polling when using rules. See the AddThresholdToMetric library documentation.

4. Enable the default Service, unless a specific configuration option is needed.

   Configuration -> Broker Control -> Services

Default Service

Field	Value
Package Name	coreProcessing-app
Service Name	Metric Abnormal Thresholding Engine
Service Program	bin/core/processing/AbnormalThresholdEngined
Service Arguments
Service Description	Holt-Winters based dynamic thresholding engine
Failover Type	Standalone (Supported: Standalone, Primary/Backup)
Status	Disabled
Privileged	(Unchecked)

Default Configuration

Name	Value	Possible Value(s)	Notes
CheckTime	900	Integer	How often (in seconds) where the application checks to see if there are new metrics to monitor and perform other actions.
LogFile	logs/MetricAbnormalThresholdEngine.log	Text, 255 characters	Relative path to Log File.
LogLevel	ERROR	OFF, FATAL, ERROR, WARN, INFO, DEBUG	Logging level used by application.
PollTime	300	Integer	How often the thresholding engine checks for violations.
Threads	3	Integer	The number of processing threads created.
DeviceGroupID	0	Integer	Optional - If specified, the thresholding engine will only look at metrics for devices in the specific group.
DeviceZoneID	0	Integer	Optional - If specified, the thresholding engine will only look at metrics for devices in the specific zone.
PreferIPv4	Enabled	Enabled/Disabled	Optional - Controls whether or not to prefer IPv4 transport for Devices. This option is only considered if both IPv4 and IPv6 are available for a device. If this config is missing, IPv6 will be preferred.

Administration Details

The following list shows the technical details needed for advanced administration of the application:

• Package - coreProcessing-app

• Synopsis - ./AbnormalThresholdEngined [OPTIONS]

• Options:

   -c, --AppConfigID N   Application Config ID (Service ID)
   -?, -h, --Help        Print usage and exit
  

• Threaded - Multi-Threaded