25.3 enhancements and patches
BMC Helix applies upgrades as described in BMC Helix Upgrade policy. BMC Helix applies upgrades and patches during Maintenance windows.
25.3.01
Configure multiple on-premises gateway instances to use the same BMC Helix object storage
If you have multiple on-premises gateway standalone instances collecting data from different sources, you can configure them to use a single BMC Helix object storage for high availability by grouping the instances into clusters and setting the HIIG_HA_CLUSTER_ID parameter.
For more information about setting the parameter, see Configuring the on-premises gateway for high availability.
Limit event data ingested from Zabbix by using additional parameters
Limit event data ingested from Zabbix by using the following parameters in BMC Helix Intelligent Integrations:
- Host Groups: Fetch events filtered by host groups. Provide the parameter values on the COLLECTOR CONFIGURATION tab in the UI.
- Tags: Fetch events filtered by tags. Provide the parameter values on the COLLECTOR CONFIGURATION tab in the UI.
- suppressed: Fetch events filtered by their status (suppressed, normal, or all events). Enable the Edit JSON option on the COLLECTOR CONFIGURATION tab and provide the parameter value.
For more information, see Integrating with Zabbix.
Limit event data ingested from Nagios Core by using a query
In addition to the out-of-the-box filters available on the COLLECTOR CONFIGURATION tab for ingesting limited event data from Nagios Core, you can use a query to specify additional parameters by which you want to filter the event data. For example, to collect events received by the nagiosadmin user, use the following query in the filterQueryString parameter: "contactname=nagiosadmin". When events are received in BMC Helix Operations Management, the source_filterQueryString field on the Others tab on the Event Details page shows the filter query.
For more information, see Integrating with Nagios Core.
Deduplicate Zabbix events by using a new policy
Events collected from Zabbix via BMC Helix Intelligent Integrations are processed in BMC Helix Operations Management according to the rules defined in the Close Old Zabbix Events - BMC Helix Intelligent Integrations policy. According to this policy, if an incoming event has the same trigger ID as an existing event, the existing event is closed, avoiding duplicate events. The policy is available on the Configuration > Event Policies page.
For more information about the policy, see Events deduplication, suppression, and closure for reducing event noise.
What else changed in this release
| Update | Product behavior in versions before 25.3.01 | Product behavior in version 25.3.01 |
|---|---|---|
| (Helix subscribers only) Separate container images for monitoring the on-premises gateway node and container health by using dashboards | Container images:
Important: You must obtain and load both the images in version 25.3.00. | Container images:
Important: Even if you don't obtain the optional images, you can continue monitoring the on-premises gateway by using events. For more information, see Monitoring BMC Helix Intelligent Integrations for streaming interruptions by using events. |
25.3.00
The following video (1:57) provides a high-level summary of the new features and enhancements in version 25.3 of BMC Helix Intelligent Integrations:
Watch the YouTube video about What’s new in BMC Helix Intelligent Integrations 25.3
Minimize operational overhead with BMC Helix object storage
In a high-availability deployment of the BMC Helix Intelligent Integrations on-premises gateway, you can use the BMC Helix object storage for backing up and restoring the on-premises gateway configuration. This approach offers lower operational overhead compared to using a private object storage, such as a standalone MinIO instance or AWS S3. The BMC Helix object storage is available only for BMC Helix subscribers.
For more information, see Configuring the on-premises gateway for high availability.
Configure the communication protocol between the on-premises gateway and Identity Management System
The BMC Helix Intelligent Integrations on-premises gateway can also communicate with the Identity Management System (IMS) over HTTPS, in addition to the existing protocol, HTTP.
Use the USE_HTTPS_IMS_URL parameter to configure HTTPS or HTTP (default) as the protocol. For more information about configuring the parameter, see Troubleshooting the BMC Helix Intelligent Integrations issues.
What else changed in this release
| Update | Product behavior in versions before 25.3.00 | Product behavior in version 25.3.00 |
|---|---|---|
| (Helix subscribers only) Separate container images for Grafana | Container images (includes images for the on-premises gateway and Grafana): bmc-hii-docker-images-<buildNumber>.tgz | Container images (separate images for the on-premises gateway and Grafana):
You must obtain and load both the images in version 25.3.00. For more information, see: |