Default language.

Configuring autoanomaly event generation

As an administrator, use the Manage Auto Anomaly Event Generation page to configure automatic anomaly event generation with fewer manual configurations. BMC Helix Operations Management generates anomaly events automatically when a metric value violates all baselines and metric deviation (in sigma) values for a specific duration.

Related topics

Autoanomalies

Manage Auto Anomaly Event Generation page

 

Important

Event policies do not apply to anomaly events. You can manually close the anomaly events from the Events page in BMC Helix Operations Management or by using the POST /events/operations/delete REST API. For more information, see Event management endpoints in the REST API. The anomaly events are automatically purged after 90 days.

 

To configure autoanomaly event generation

  1. In BMC Helix Operations Management, select Configuration > Auto Anomalies.
  2. On the Manage Auto Anomaly Event Generation page, click the toggle key to enable or disable autoanomaly event generation.
    By default, anomaly event generation is disabled for a tenant.
    If the feature is disabled, the autoanomaly events are closed. The autoanomaly events continue to remain open for any other configuration change. To close the events, manually close them from the Events page or by using the close API.
  3. Select one of the following options to generate anomaly events:

    • KPI metrics
      Generates anomaly events for only the key performance indicators (KPIs) metrics. Metrics are marked as KPIs at the PATROL Agent and integration level.
      To learn more about performance and KPI metrics, see Monitoring solutions in BMC Helix Operations Management.
      This option is the default option.

    • All performance metrics
      Generates anomaly events for statistical attributes that have measurement units such as %, GB, MB, and so on.
  4. Click Manage Metrics to modify the configuration for autoanomaly generation.
  5. On the Manage Metrics page, under the Metric Name column, select the metric for which you want to modify the configuration.
  6. Select one of the following options from the Configuration column:
    • Generate autoanomaly events only for low baseline violation
    • Generate autoanomaly events only for high baseline violation
    • Generate autoanomaly event
    • Don't generate autoanomaly events
      The following image shows the Manage Metrics page.
      Manage Metrics page
  7. Click Update.
  8. Specify the metric deviation value in sigma.
    Deviation indicates how far the metric value is from the mean. By default, the deviation value is set to 3 and must range between 1 and 5.
    Anomalies are generated with a small deviation for a lower sigma number and a large deviation for a higher sigma number.
    To learn how sigma deviation works, see Variate-Policies.
  9. Specify the duration in minutes for which the metric violates the baseline and metric deviation.
    By default, the duration is 15 minutes and cannot exceed 30 minutes. The system generates anomaly events if the metric value continuously violates the baseline and metric deviation values for the specified duration.
  10. Select the severity of the anomaly event.
    Severity can have the following values:
    1. Information (Default value)
    2. Warning
    3. Minor
    4. Major
    5. Critical
  11. Click Save.
  12. Click Reset to default values to reset the configuration settings, modify the required fields, and click Save.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*