24.1 enhancements and patches
BMC applies upgrades as described in BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows..
24.1.02
Collect metrics data from Google Analytics
Collect metrics data from the funnel exploration report in Google Analytics.
For more information, see Integrating-with-Google-Analytics.
Updates to the Catchpoint policy
The behavior of the Close Old Catchpoint Events - BMC Helix Intelligent Integrations policy is updated due to the updates in the Catchpoint version Cheetah:
- The policy creates a new event for each node on which a test was performed and the test triggered the Critical level alert in Catchpoint. After the new event is created, the policy closes and updates the old event with notes containing the event ID of the new event, node ID, and test ID.
- If an incoming event contains the Improved level alert triggered by a test on any of the nodes, the policy closes all the old events generated for all the nodes on which the test was performed.
For more information, see Event-deduplication-suppression-and-closure-for-reducing-event-noise.
24.1.01
Enhanced UI experience for topology data collection from specific resource groups in Microsoft SCOM
In the Microsoft SCOM connector, the SCOMGroups field has been replaced with two new fields, ResourceGroups and UseResourceGroups. The combined usage of these new fields enables you to collect topology data from specific resource groups.
For more information, see Integrating-with-Microsoft-SCOM.
24.1.00
The following video (1:55) provides a high-level summary of the new features and enhancements in version 24.1 of BMC Helix Intelligent Integrations:
Watch the YouTube video about What’s new in BMC Helix Intelligent Integrations 24.1
Collect topology data from Zabbix by using additional filters
Collect topology data from Zabbixfiltered by host groups, applications, and tags.
For more information, see Integrating-with-Zabbix.
Collect alerts from Amazon Managed Service for Prometheus by using an additional filter
Collect alerts from Amazon Managed Service for Prometheus (AMP) filtered by status.
For more information, see Integrating-with-Amazon-Managed-Services-for-Prometheus-to-collect-events.
Collect alerts from Prometheus by using an additional filter
Collect alerts from Prometheus filtered by status.
For more information, see Integrating-with-Prometheus-to-collect-events-via-API.
Collect events from CA UIM by using an additional filter
Collect event data from CA UIM filtered by status.
For more information, see Integrating-with-CA-UIM.
Change in the sequence of filters to collect metrics data from Amazon Managed Service for Prometheus
The sequence of the Jobs and Metric Namespaces fields has been swapped to improve the collection of metric data from Amazon Managed Service for Prometheus (AMP). You can collect data even for those metric namespaces that are associated with specific jobs.
For more information, see Integrating-with-Amazon-Managed-Services-for-Prometheus-to-collect-metrics.
Change in the sequence of filters to collect metrics data from Prometheus
The sequence of the Jobs and Metric Namespaces fields has been swapped to improve the collection of metric data from Prometheus Metrics. You can collect data even for those metric namespaces that are associated with specific jobs.
For more information, see Integrating-with-Prometheus-to-collect-metrics-via-API.
Collect alerts from SolarWinds NPM by using an additional filter
Collect alerts from SolarWinds NPM filtered by status.
For more information, see Integrating-with-SolarWinds-NPM.
