Configuring ML-based situations

The Manage Situations settings determine the conditions to correlate events into ML-based situations and correlate related situations to form a group of primary or similar situations. 

As a tenant administrator, enable the AIOps Situations feature from the Manage Product Features page to view the Manage Situations page. From this page, you configure these settings to allow operators or site reliability engineers (SREs) to monitor ML-based situations.

Important

These configuration changes apply only at the tenant level.

Related topics

Roles-and-permissions

Enabling-the-AIOps-features

Monitoring-key-performance-indicators-and-entities

Monitoring-situations

Investigating-ML-based-situations

FAQ

To configure situation settings

  1. On the BMC Helix AIOps console, click Manage Situations under Configurations.

    Configurations_Manage_Situations.png
     

  2. On the Manage Situations page, configure the settings based on the following options:

    Options

    Description

    Drag the Correlation Event Time Window (in mins) slide bar to set the window.
    By default, it is set to 15 minutes.

    Determines whether two events with the same signature can be correlated, provided the signatures are also correlated from the topology and temporal aspects. If all these conditions are met, the events are correlated and any event that comes after the set time limit is not correlated into a situation.

    Example: You have an event sequence with three events occurred when CPU utilization is at 90%, 93%, and 97% at 05:00 hr, 05:10 hr, and 05:13 hr. All these events have the same event signature. According to the correlation event time window, they are grouped into a situation, as they are temporally and topologically related.

    Drag the Situation Stability Window (in mins) slide bar to set the window.
    By default, it is set to 30 minutes.

    Determines situations' stability or saturation. The situation attains saturation or stability if there are no new event signatures to be aggregated within the set time limit. If there are new event signatures to be aggregated, the stability window is reset until there no more new event signatures.

    Expand Advanced Settings to perform the following tasks:

    Toggle the Show Policy-based Situations option to show or hide the policy-based situations along with the ML-based situations.
    By default, this option is enabled.

    Determines whether to show or hide the policy-based situations on the Overview and Situations pages. When enabled, the policy-based situations are listed along with the ML-based or AIOps situations in the console.

    Drag the Expiry of Similar Situation Group (in days) slide bar to set the days.
    By default, it is set to 30 days.

    Determines the maximum number of idle days for a group of similar situations to be marked as expired. A group is expired if no new similar situations are added to it within this period. After the expiry time, any new similar situation is not associated to the expired group.

    Drag the Similar Situation Detection Window (in hours) slide bar to set the window.
    By default, it is set to 24 hours.

    Determines the hourly interval to detect similar situations and form the groups. The similar situations detection policy runs according to the specified interval and a group is formed if two or more stabilized situations are identified to have similar message, impact, and node ID (service node). Based on the identified similarity, either the new situations are added to an existing group or a new group is created.

  3. Save the changes.

 

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