StandardThresholdEngined
The Oracle Communications Unified Assurance 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 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.
You can run this application as a service using the Services UI.
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:
-
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 documentation in Unified Assurance Developer's Guide.
-
-
Enable the default Service, unless a specific configuration option is needed.
Default Service
The following table shows the settings for the default service. Actual values are in bold, descriptions of values are in plaintext.
Field | Value |
---|---|
Package | coreProcessing-app |
Name | Metric Standard Thresholding Engine |
Program | bin/core/processing/StandardThresholdEngined |
Arguments | This field is blank. There is no default value. |
Description | Default Value, Util, and Availability Thresholding based on Daily Tables |
Failover Type | Standalone (Supported: Standalone, Primary, Redundant/Backup) |
Status | Disabled |
Privileged | This option is not selected. |
See Services in Unified Assurance User's Guide for general information about the settings for services.
See Using Application Primary/Backup Failover for more information about the different failover types.
Default Configuration
The following table shows the default configurations for the application. Actual values are in bold, descriptions of values are in plaintext.
Name | Default Value | Possible Values | Notes |
---|---|---|---|
BaseRules | processing/event/threshold/base.rules | Text, 255 characters | The relative path to the application Base Rules file. |
BranchDir | core/default | Text, 255 characters | The relative path to the rules directory. |
CheckTime | 900 | An 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 | The relative path to the application Include Rules file. |
LoadRules | processing/event/threshold/base.load | Text, 255 characters | The relative path to the application Load Rules file. |
LogFile | logs/MetricStandardThresholdEngine.log | Text, 255 characters | The relative path to the log file. |
LogLevel | ERROR | OFF, FATAL, ERROR, WARN, INFO, DEBUG | The logging level for the application. |
PollTime | 60 | An integer | How often the thresholding engine should check for violations, in seconds. |
Threads | 3 | An 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 | An integer | (Optional) Number of database threads to be created. If not specified, defaults to a third (rounded up) of ThresholdThreads application configuration. |
DeviceGroupID | This field is blank. There is no default value. | The name of any available device group. | (Optional) If specified, the thresholding engine will only look at metrics for devices in the specific group. |
DeviceZoneID | This field is blank. There is no default value. | All Zones or the name of any available device zone. | (Optional) If specified, the thresholding engine will only look at metrics for devices in the specific zone. |
FieldSetFile | This field is blank. There is no default value. | Text, 255 characters | (Optional) Path to csv file containing custom list of fields that will be used when inserting data. (Requires InsertSQLFile.) |
InsertSQLFile | This field is blank. There is no default value. | Text, 255 characters | (Optional) Path to file containing custom SQL Insert statement for handling of event inserts. (Requires FieldSetFile.) |
Maintenance | Disabled | Enabled or 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 or 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 | An integer | Number of threshold threads to be created. Enabled the checking of thresholds in the application instead of the Default Threshold Engine. If not specified, application threshold checking is disabled. |
Administration Details
The following list shows the technical details you will need for advanced administration of the application:
-
Package: coreProcessing-app
-
Package:
./StandardThresholdEngined [OPTIONS]
-
Options:
-c, --AppConfigID N Application Config ID (Job ID) -?, -h, --Help Print usage and exit
-
Threaded: Multithreaded