MissingDataThresholdEngine

The Oracle Communications Unified Assurance Metric Missing Data Threshold Engine generates violations based upon data existing for a metric, but if the metric data then stops being inserting for whatever reason, a threshold violation will be generated when the scheduled job is ran. This can detect when polling suddenly stops and does not resume either from an application failure, network issues, etc. The application will not detect skipped polls or intermittent inserts.

You can run this application as a scheduled job using the Jobs UI.

Missing Data Threshold Engine Setup

Note:

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

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

    Configuration -> Metrics -> Thresholds -> Thresholds

    • Type must be: Missing Data

  2. Add thresholds to metrics. This can be done in several ways:

  3. Enable the default Job, unless a specific configuration option is needed.

    Configuration -> Broker Control -> Jobs

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 Missing Data Threshold Engine
Program bin/core/processing/MissingDataThresholdEngine
Arguments This field is blank. There is no default value.
Description Generate Missing Data of Pollers
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/MetricMissingDataThresholdEngine.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

Administration Details

The following list shows the technical details you will need for advanced administration of the application: