Assure1 Metric Standard Threshold Engine¶
Overview¶
The Assure1 Metric Standard Threshold Engine is used to monitor the metric data, and if the metric goes over (or under, depending on the metric) a value within the specified time range. This threshold engine is best used for monitoring availability of a device or metrics with a discrete levels, such as 0% or 100% utilization. Environments with a large variety of Time Ranges and/or Poll Intervals may wish to use multiple threshold engines split by Device Group and/or Device Zone to maintain performance gains.
Note
As part of using the other thresholding engines (Abnormal, Missing Data, Trend), the "Metric Standard Thresholding Engine" must also be enabled and running to process threshold violation messages into events.
Standard Threshold Engine Setup¶
-
Add Threshold(s) or modify existing Threshold(s):
Configuration -> Metrics -> Thresholds -> Thresholds
- Type must be:
Standard
- Type must be:
-
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:
-
Added to the metric during polling when using rules. See the "AddThresholdToMetric" library documentation.
-
-
Enable the default Service, unless a specific configuration option is needed.
Default Service¶
Field | Value |
---|---|
Package Name | coreProcessing-app |
Service Name | Metric Standard Thresholding Engine |
Service Program | bin/core/processing/StandardThresholdEngined |
Service Arguments | |
Service Description | Default Value, Util, and Availability Thresholding based on Daily Tables |
Failover Type | Standalone (Supported: Standalone, Primary/Backup) |
Status | Disabled |
Privileged | (Unchecked) |
Default Configuration¶
Name | Value | Possible Values | Notes |
---|---|---|---|
BaseRules | processing/event/threshold/base.rules | Text, 255 characters | Relative path to Base Rules. |
BranchDir | core/default | Text, 255 characters | Relative path to Rules directory. |
CheckTime | 900 | Integer | This entry is used to check the configuration for changes the specified number of seconds, and also to get a list of devices that do not have a maintenance window. |
IncludeRules | processing/event/threshold/base.includes | Text, 255 characters | Relative path to Include Rules. |
LoadRules | processing/event/threshold/base.load | Text, 255 characters | Relative path to Load Rules. |
LogFile | logs/MetricStandardThresholdEngine.log | Text, 255 characters | Relative path to Log File. |
LogLevel | ERROR | OFF, FATAL, ERROR, WARN, INFO, DEBUG | Logging level used by application. |
PollTime | 60 | Integer | How often the thresholding engine should check for violations, in seconds. |
Threads | 3 | Integer | Number of process threads created. The engine takes a third of this value (rounded up) for database threads unless overridden by the "ThresholdThreads" application configuration. |
DBThreads | 3 | Integer | Optional - Number of database threads to be created. If not specified, defaults to a third (rounded up) of "ThresholdThreads" application configuration. |
DeviceGroupID | Combobox of available Groups | Optional - If specified, the thresholding engine will only look at metrics for devices in the specific group. | |
DeviceZoneID | Combobox of available Zones | Optional - If specified, the thresholding engine will only look at metrics for devices in the specific zone. | |
FieldSetFile | Text, 255 characters | Optional - Path to csv file containing custom list of fields that will be used when inserting data. (Requires InsertSQLFile.) | |
InsertSQLFile | Text, 255 characters | Optional - Path to file containing custom SQL Insert statement for handling of event inserts. (Requires FieldSetFile.) | |
Maintenance | Disabled | Enabled/Disabled | Optional - If a device is in a maintenance window during the current cycle, it will be removed from the list of devices that the thresholding engine checks. |
SendAllViolations | Disabled | Enabled/Disabled | Optional - If set to "Enabled", every threshold violation (regardless of current state) will create a notification. Otherwise, only violations that changed state will be sent e.g. only Active violations from a Clear state and Clear messages from an Active state. |
ThresholdThreads | 3 | Integer | TBD |
Administration Details¶
The following list shows the technical details needed for advanced administration of the application:
-
Package - coreProcessing-app
-
Synopsis -
./StandardThresholdEngined [OPTIONS]
-
Options:
-c, --AppConfigID N Application Config ID (Job ID) -?, -h, --Help Print usage and exit
-
Threaded - Multi-Threaded