25.2 enhancements and patches
BMC Helix applies upgrades as described in BMC Helix Upgrade policy. BMC Helix applies upgrades and patches during Maintenance windows.
25.2.01
Configure the scheduler interval for heartbeat events
Use the notificationSchedulerInterval parameter to configure the time period after which heartbeat events should be sent by BMC Helix Intelligent Integrations when events or metrics data is streamed. The default value of this parameter is 5 minutes.
Heartbeat events are no longer sent for every batch of events or metrics received in BMC Helix Operations Management, thereby reducing event storms.
For more information, see Monitoring BMC Helix Intelligent Integrations for streaming interruptions by using events.
Improved mapping of the AWS CloudWatch alarm attributes
BMC Helix Intelligent Integrations maps one of the following alarm attributes to the source_hostname event slot in BMC Helix Operations Management:
- PublicDnsName
- PublicIpAddress
- InstanceID
- Name tag
- Tags
The mapping considers the above priority order to map an attribute. If an attribute is missing or its value is empty, the next attribute in the sequence is considered for mapping.
This mapping helps to obtain the source host name, which in turn makes reporting and analytics more precise.
For more information, see Integrating with AWS CloudWatch.
25.2.00
The following video (1:58) provides a high-level summary of the new features and enhancements in version 25.2 of BMC Helix Intelligent Integrations:
Watch the YouTube video about What’s new in BMC Helix Intelligent Integrations 25.2
Monitor BMC Helix Intelligent Integrations for streaming interruptions
Monitor BMC Helix Intelligent Integrations for any interruptions in events or metrics data streaming from third-party sources by using heartbeat and notification events.
When events or metrics are streamed from a source, BMC Helix Intelligent Integrations sends heartbeat events to BMC Helix Operations Management for the source. If streaming stops for any reason, a notification event is generated in BMC Helix Operations Management, indicating that streaming has stopped for that source and there is an issue with data collection. You can start troubleshooting the issue from that point onwards.
For more information, see Monitoring BMC Helix Intelligent Integrations for streaming interruptions by using events.
Collect metrics from BMC Netreo via API
Collect metrics from BMC Netreo via API 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 BMC Netreo via API.
Collect SNMPv3 traps from multiple agents through a single connection instance
Collect traps from multiple SNMPv3 agents through a single SNMP connection instance by using the new option Use Configuration File.
Store the details of all the agents that are sending traps in a configuration file, and provide the file name in the Configuration File Name field. BMC Helix Intelligent Integrations collects data from all agents whose details are present in the configuration file.
For more information, see Integrating with SNMP-managed devices.
Collect vendor-specific SNMP traps by using a custom JSLT
Use a custom JSLT to collect vendor-specific traps from SNMP agents.
By default, all incoming traps are mapped to the SNMP_TRAP event class. When you use a custom JSLT, SNMP traps are mapped to vendor-specific custom classes.
For more information, see Integrating with SNMP-managed devices.
Collect topology data from Microsoft SCOM only for the directly impacted group members
Collect topology data from Microsoft SCOM by using a new option Directly Impacted Resource Groups Members Only. Select this option to collect data for only those resource group members that are directly impacted by events.
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 and P1 is impacted by events, data is collected only for VM1 and VM2 and not for P1.
For more information, see Integrating with Microsoft SCOM.
