24.4 enhancements and patches


Review the BMC Helix Intelligent Integrations and BMC Helix Developer Tools 24.4 enhancements and patches for features that will benefit your organization and to understand changes that might impact your users.

Version

SaaS

On premises

Fixed issues

Updates and enhancements

24.4.02

✅️

✅️

24.4.01

✅️

✅️

24.4.00

✅️

✅️

For updates and enhancements in the previous release and its patches, see Release-notes-and-notices.

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



24.4.02


Collect data from Microsoft SCOM only for directly connected group members

Collect events and metrics data from Microsoft SCOM by using a new option Directly Impacted Resource Groups Members OnlySelect this option to collect data for only those resource group members that are directly connected to a resource group.

For example, a resource group, RS1, has two virtual machines as group members: VM1 and VM2. VM1 has an associated printer, P1. If you select this option, data is collected only for VM1 and VM2 and not for P1.

For more information, see Integrating with SCOM.

Directly_Impacted_Resource_Groups__members_Only.png


24.4.01



Filter events and metrics data from Icinga by using a query

In addition to using regex to filter events and metrics data, you can use a query to filter the events and metrics data from Icinga. Queries are helpful when the data being collected might change over a period of time.

For example, use the query to collect events for all those services whose state is OKIf the state of a service changes to INACTIVE after the data collection interval you have specified, events are not collected for that service.

Use the entityType parameter to specify the entity for which you want to collect data and the filterQueryString parameter to specify the filter query.

For more information, see Integrating-with-Icinga.

Icinga_Query_Filter.png


AWS_CW_ApiGateway.png

Collect alarms and metrics data for a new namespace from AWS CloudWatch

Collect alarms and metrics data for a new namespace ApiGateway of REST API type from AWS CloudWatch.

Receive alarms as events in BMC Helix Operations Management and measure the health of your system by processing the received events with BMC Helix Operations Management capabilities.

Take corrective actions and reduce overall outages by using policies in BMC Helix Operations Management to generate alarms when the value of a received metric goes above or below a set threshold.

For more information, see Integrating-with-AWS-CloudWatch.


24.4.00


The following video (1:56) provides a high-level summary of the new features and enhancements in version 24.4 of BMC Helix Intelligent Integrations: 

icon_play.pngWatch the YouTube video about What’s new in BMC Helix Intelligent Integrations 24.4


Collect metrics from BMC Stackify

Collects metrics from BMC Stackify and receive them in BMC Helix Operations Management.

Take corrective actions and reduce overall outages by using policies in BMC Helix Operations Management to generate alarms when a metric value goes above or below a set threshold.

For more information, see Integrating with Stackify.

Stackify_connector_new.png


AWS-CloudWatch-filters.png

Collect alarms from AWS CloudWatch by using additional filters

The Alarm Names filter to collect alarms from AWS CloudWatch is replaced with the following filters: Namespaces, Alarm Names Regex, and Metric Names Regex. These filters help you to collect data for specific namespaces, alarms, and metrics. For more information, see Integrating-with-AWS-CloudWatch.

After you upgrade to version 24.4, the existing connector instances are not updated with these filters automatically. You need to either create a new connector instance or stop the existing data stream and create a new data stream. For information about editing an existing connector for data streams, see Editing-and-deleting-integrations and Starting-or-stopping-data-streams.



Deploy and upgrade the on-premises gateway by using a script

You can deploy and upgrade the on-premises gateway by using the gateway_deployment.sh script. The script prompts you to enter the required information, such as access key and host name, during the deployment and upgrade process. You no longer need to store the information in the cred.json file manually.

For more information, see:


What else changed in this release

Update

Product behavior in versions before 24.4.00

Product behavior in version 24.4.00

Policy to collect events from BMC Netreo renamed

Policy name: Update NetreoIncident Events

Policy name: Update Netreo Events

 

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