25.2 enhancements and patches

Review the BMC Helix AIOps 25.2 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

For a list of recent updates and enhancements across multiple versions, see Release notes and notices.

BMC Helix, Inc. applies upgrades as described in the BMC Helix Upgrade policy. BMC Helix, Inc. applies upgrades and patches during Maintenance windows.

25.2.00

Learn about the new features and enhancements in this release in the following video (2:35):

Watch the YouTube video about What's new in BMC Helix AIOps 25.2

Determine the health score of your service based on impact severityEdit

In addition to the existing service health score computation mechanism, which is based on node kind, BMC Helix AIOps offers a new computation mechanism. Use this mechanism to view a service health score based on the severity of the impact on the nodes of that service. The score of the node with the highest impact (lowest score) is considered the health score of the service.

You can select the computation mechanism for all the services from the Manage Service Health page.

Enhanced baseline graphs for health indicatorsEdit

On the service details page, you can view the baseline graphs for health indicators. These graphs include daily, weekly, and monthly baseline values, in addition to the hourly baseline values. Each baseline value is represented by a unique color.

For more information, see Monitoring service health indicators.

View historical and closed prediction eventsEdit

On the Predictions page, in addition to the open prediction events, you can view all the closed prediction events by using the Status filter. By default, closed predictions for the last 24 hours are displayed. To refine your view, use the time filter to display prediction events from the past 7 days, 30 days, or Custom.

All past prediction events are available in a single, consolidated view. The Past Predictions cross-launch link is no longer available on the Predictions page; however, you can view the Prediction Analysis dashboard in BMC Helix Dashboards. 

For more information, see Monitoring service predictions.

Prediction Analysis dashboard updates

On the Prediction Analysis dashboard, view event slots, like host name, metric value, threshold value, timestamp, and prediction event service key, for enhanced visibility into prediction events. For more information, see the Prediction Analysis dashboard.

Use autoanomaly detection to define thresholds for health indicators

Instead of manually configuring thresholds on health indicators with alarm policies, you can use autoanomaly detection to define thresholds on health indicators dynamically. For more information, see Autoanomalies. By using both methods to define baselines and thresholds, BMC Helix AIOps empowers you to receive accurate predictions and more precise forecasting tailored to your environment. For more information, see Monitoring service predictions.

View only open incidents associated with the serviceEdit

On the Service details and the Overview pages, the incident count includes incidents only in the Open, Assigned, In Progress, Pending, and Reopened states. The Closed, Cancelled, and Resolved incidents are not included in this count. This enhancement improves incident visibility, allowing teams to focus on the current issues. 

For more information, see Monitoring service health.

 Edit

Configure infinite sessions for BMC Helix AIOps users

Some operators or site reliability engineers (SREs) might require continuous access to the Service Heatmap view to monitor service impact. For such users, configure session settings in BMC Helix SSO Admin Console to ensure sessions remain active indefinitely, eliminating the need for repeated authentication. For more information, see Configuring infinite user sessions.

Enhanced mean time to resolve (MTTR) computation for incidents

MTTR is now computed based on the time taken to resolve an incident, rather than the time taken to close it. By focusing on when the incident is actually resolved, this approach provides improved MTTR for resolving problems. For more information, see Total incident count and mean time to resolve (MTTR) indicators for a reliable incidence-response process.

Improved user experience on the Situations pageEdit

The following enhancements have been made to the Situations page to improve your experience while monitoring or investigating situations: 

• Case-insensitive search
• Search by service name
  If you search with a service name, all situations created for the service are displayed.

For more information, see Monitoring situations and Investigating ML-based situations. 

View notes for a situation

View notes added to a situation by clicking the Show Notes link on the situation details page.

For more information, see Monitoring situations and Investigating ML-based situations. 

Configure a default time zone for your tenant

By default, BMC Helix AIOps considers the browser's time zone. Tenant administrators can specify the time zone for all users in BMC Helix Portal, ensuring that activities across multiple locations remain synchronized. In addition, you can specify your preferred time zone, which overrides the time zone specified by the administrator. After you configure this setting in BMC Helix Portal, it is available in BMC Helix AIOps. For more information, see Configuring a time zone for your tenant.

Vulnerability Manager roleEdit

The Vulnerability Manager role is available out-of-the-box to monitor and investigate vulnerabilities in BMC Helix AIOps. As an administrator, assign the role to users in BMC Helix Portal. For more information, see Roles and permissions.

The vulnerability manager can perform the following tasks:

Create and assign categories to vulnerabilitiesEdit

As a vulnerability manager, you can create and assign categories to vulnerabilities by using the REST API. This enhancement helps you prioritize the vulnerabilities and assign them to the appropriate remediation owners. After the categories are assigned, they are displayed as part of the vulnerability details.

For more information, see Assigning categories to vulnerabilities by using the REST API.

Improved user experience on the Vulnerabilities pageEdit

The following information is available on the Vulnerabilities page to help the vulnerability manager prioritize remediation: 

• First Reported: View the date the vulnerability instance was first recorded and remediate the earliest recorded vulnerability.
• Status: Observe the status of a vulnerability instance (Affected, Not Affected, and Under Investigation) and determine which vulnerability is ready for remediation.
• Categories: Assign categories to the vulnerabilities according to their area of impact. 
• Source: View the source of the vulnerability and plan remediation of all vulnerabilities from a particular scanning system.
• SLA status: Monitor the service level agreement (SLA) status of the assets to determine how many days they are within the SLA or exceeding the SLA, and plan remediation accordingly.

For more information, see Investigating vulnerabilities.