Table of Contents

Behavioral anomaly detection


This section contains information about behavioral anomaly detection in the Alarm Console. For more information on the functionality of this feature in general, see Working with behavioral anomaly detection.

Whenever behavioral anomaly detection finds an anomalous level shift, trend change, variance change, or flatline for a parameter, a "suggestion event" is generated in the Alarm Console.

These suggestion events can be viewed in a dedicated suggestion events tab, as alarms with severity "Information" and source "Suggestion Engine”. See Adding and removing alarm tabs in the Alarm Console.

You can also configure alarm templates to have alarms generated instead of suggestion events, depending on the parameter and the type of anomaly. See Configuring anomaly detection alarms for specific parameters.

Please note the following regarding suggestion events:

  • Currently, no suggestion events are generated for outliers and unlabeled change points.

  • Suggestion events generated to indicate a behavioral anomaly are automatically cleared 2 hours after their creation time or their last update time. From DataMiner 10.2.11/10.3.0 onwards, they are also cleared in case a new behavioral change is detected that ends the previous anomalous behavioral change. For example, when an alarm was created for an anomalous level increase at 1 PM, and a behavioral change point is detected at 2 PM when the level drops again, then the alarm created at 1 PM will be closed at 2 PM.

  • Depending on the DataMiner version, different limitations are in place as to how many suggestion events can be generated for anomalous behavioral changes:

    • From DataMiner 10.4.0 [CU2]/10.4.5 onwards, at most 500 suggestion events related to behavioral anomaly detection can be shown in the active suggestion events tab of the Alarm Console.
    • From DataMiner 10.4.0 [CU1]/10.4.4 onwards, at most 50 new suggestion events per hour per type of anomaly (i.e. level shift, trend change, flatline, or variance change) can be generated per DataMiner Agent. There is no limit to the maximum number of anomaly alarm events, i.e. alarm events for parameters that have explicit anomaly alarm monitoring configured in the alarm template.
    • From DataMiner 10.2.11/10.3.0 onwards, suggestion events are only created for the most significant changes, and per hosting DataMiner Agent there can be at most 500 open suggestion events related to behavioral anomaly detection.
    • Prior to DataMiner 10.2.11/10.3.0, suggestion events are created for all anomalous behavioral changes that do not have alarm monitoring enabled.