Configuring Event generation settings

You can configure Event generation settings by leveraging the trained Machine Learning models to: 

• Automate actions
• Gain real-time insights
• Improve operational efficiency in response to changing conditions and data patterns

You can set up automated event generation based on the predictions and insights that the trained machine-learning models generate. By configuring Event generation settings, you can automate decision-making based on the output of machine learning models. When a threshold or condition is met, the BMC Helix Edge automatically generates events to initiate actions, notifications, or alerts. For example, an event can trigger a maintenance request to prevent downtime if a predictive maintenance model forecasts equipment failure.

You can use these settings to customize and define the criteria under which BMC Helix Edge generates events. You can set rules, thresholds, and conditions to a specific use case and business requirements.

Before you begin

• Make sure you configure the Machine Learning model in BMC Helix Edge. See 2025-02-15_12-25-53_Configuring Machine Learning models.
• Make sure you completed the training process for the specific machine learning model. See 2025-02-15_12-25-54_Training a machine learning model.

To configure the event setting

With Event Identification, Severity Thresholds, and Stabilization Period settings, you can define and fine-tune the event generation process to make sure that events are meaningful, actionable, and aligned with your operational needs and priorities.

1. On the BMC Helix Edge page, select Machine Learning.
2. In the list of trained models, identify the specific trained model to configure Event generation settings.
3. Clickto expand the model.
4. In the expanded model panel, identify the model for configuring Event generation settings and select Actions > Event generation settings. 
   BMC Helix Edge displays the Event generation settings panel:
   
5. In the Event generation settings panel, perform the following steps:

   1. Complete the following fields to define details related to identifying and describing an event in a monitoring or alerting system:

      Field name	Description
      Event name	Specify a unique name for the event. The event name identifies and references the event in the system. Make sure that this field has a descriptive and recognizable name that indicates the nature or purpose of the event.
      Event description	Provide a detailed event description in this field. The event description serves to clarify the event's significance, its triggers, and the expected actions or responses associated with it. A well-written description helps users understand the context and importance of the event.

   2. To define the criticality level of the event, configure the threshold level by completing the following fields:

      Field name	Description
      Minor	Use this slider control to adjust an event for a minor threshold. This threshold represents events of lower severity. The minor severity events indicate minor issues or situations that require minimal attention or intervention. They might not have an immediate impact on operations.
      Major	Use this slider control to adjust an event for a major threshold. Events falling under this threshold have moderate severity levels. Major severity events suggest situations that need attention and potential action but might not be emergencies. They indicate conditions that you must monitor and address in a reasonable time.
      Critical	Use this slider control to adjust an event for a critical threshold. Critical severity events are critical and require immediate attention. These events signify significant issues, emergencies, or situations that demand rapid response and resolution. They indicate conditions that can impact operations or safety.

   3. Complete the following field to set repeatable occurrences and set the time interval during which the system monitors the event in the Stabilization period pane:

      Field name	Description
      Repeating occurrences	Use this field to list conditions or patterns that must be repeated before triggering an event. When you specify this option, BMC Helix Edge generates events only if the specified condition persists and is not a temporary anomaly. For example, you might set up a condition that says, "Temperature exceeds 90 degrees for at least three consecutive readings in 60 seconds."

6. Click Save.