MissingDataThresholdEngine

The Oracle Communications Unified Assurance Metric Missing Data Threshold Engine generates threshold violation events when the scheduled job detects that data exists for a metric but has stopped being inserted. This engine can detect when polling suddenly stops and does not resume, due to an application failure or network issues. It does 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 thresholds or modify existing thresholds by using the Thresholds UI. Set Type to Missing Data for these thresholds.

  2. 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.

  3. Enable the default Metric Missing Data 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.

  4. 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 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.
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.
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.
PreferIPv4 Enabled Enabled or Disabled Whether IPv4 or IPv6 is preferred for communication with devices, when both are available. If this configuration is missing, IPv6 will be preferred.

Best Practice

The default job is configured to run at 12:07am every day. This job should be run after all metric polling is complete to ensure valid results.

Administration Details

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