TrendThresholdEngine
The Oracle Communications Unified Assurance Metric Trend Threshold Engine monitors the linear regression trend of metrics and monitors both positive and negative changes to make soft predictions. This threshold engine is best used for monitoring metrics such as disk space or bandwidth utilization. It monitors the following thresholds:
-
Trend % Change: These thresholds check if a metric increases or decreases more than a specified amount over a specified time period, and create an event if crossed. For example, if the bandwidth rate of change is greater than 10%, based on a week's data.
-
Trend Prediction: These thresholds use the linear regression trend to predict if the value will reach a given value within a specified time period, and create an event if so. For example, if the disk will be a 90% in 6 months or sooner.
You can run this application as a scheduled job using the Jobs UI.
Trend Threshold Engine Setup
Note:
As part of using the Trend Threshold Engine application, the Metric Standard Thresholding Engine must also be enabled and running to process threshold violation messages into events.
-
Add thresholds or modify existing thresholds by using the Thresholds UI. Set Type to Trend % Change or Trend Prediction for these thresholds.
-
Add the thresholds to metrics. You can do this in the following ways:
-
Manually, by using the Metrics UI.
-
Automatically, during metric creation, using polling assignments or polling policies. See Polling Assignments and Polling Policies in Unified Assurance User's Guide.
-
Automatically, during polling, using rules. See AddThresholdToMetric in Unified Assurance Developer's Guide.
-
-
Enable the default Metric Trend Threshold Engine job, or create a custom job using specific configuration options.
See Jobs in Unified Assurance User's Guide for information about the Jobs UI.
-
Ensure that the Metric Standard Thresholding Engine service is enabled.
See Services in Unified Assurance User's Guide for information about the Services UI.
Default Scheduled Job
The following table shows the settings for the default job. Actual values are in bold, descriptions of values are in plaintext.
| Field | Value |
|---|---|
| Package | coreProcessing-app |
| Name | Metric Trend Threshold Engine |
| Program | bin/core/processing/TrendThresholdEngine |
| Arguments | This field is blank. There is no default value. |
| Description | Generate Trend Threshold Violations |
| Failover Type | Standalone (Supported: Standalone, Primary, Redundant/Backup) |
| Status | Disabled |
| Privileged | This option is not selected. |
| Minutes | 7 |
| Hours | 0 |
| Days | * |
| Months | * |
| WeekDays | * |
See Jobs in Unified Assurance User's Guide for general information about the settings for jobs.
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 |
|---|---|---|---|
| LogFile | logs/MetricTrendThresholdEngine.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. |
| Threads | 3 | An integer | The number of processing threads created. |
| 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 | All Zones | The name of any available device zone. | (Optional) If specified, the thresholding engine will only look at metrics for devices in the specific zone. |
| 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. |
Best Practices
-
The default job configuration is to run at 12:07am every day. This job should be run after all metric polling is complete to ensure valid results.
-
This job should run as often as the shortest time window in order to accurately alert on thresholds. e.g. If a time window for a threshold is less than 1 day, this job will need to be updated to run more than once a day.
Administration Details
The following list shows the technical details you will need for advanced administration of the application:
-
Package: coreProcessing-app
-
Package:
./TrendThresholdEngine [OPTIONS] -
Options:
-c, --AppConfigID N Application Config ID (Job ID) -?, -h, --Help Print usage and exit -
Threaded: Multithreaded