23.3 enhancements and patches
BMC applies upgrades as described in BMC Helix Upgrade policy. BMC applies upgrades and patches during Maintenance windows..
23.3.02
Collect alerts from Dynatrace via webhook
Collect alerts from Dynatrace via the webhook mechanism.
For more information, see Integrating-with-Dynatrace-via-webhook.
Collect topology data filtered by business applications in ServiceNow
Collect topology data from ServiceNow for specific business applications.
For more information, see Integrating-with-ServiceNow.
Enhanced UI experience for events and metrics data collection for specific resource groups in Microsoft SCOM
In the Microsoft SCOM connector, the SCOMGroups field has been replaced with the following new fields, ResourceGroups and UseResourceGroups. The combined usage of these new fields enables you to collect events and metrics data from specific resource groups.
For more information, see Integration with Microsoft SCOM.
Connect to SAP HANA by using the Transport Layer Security protocol
Use the TLS Encryption option to encrypt the Transport Layer Security (TLS) communication between BMC Helix Intelligent Integrations and SAP HANA.
For more information, see Integrating-with-SAP-HANA.
Updates in the port numbers when using the on-premises gateway for data collection via the webhook mechanism
If you are collecting data from a third-party product by using the BMC Helix Intelligent Integrations on-premises gateway via the webhook mechanism, access the UI by using port 7457 (HTTP) or 7443 (HTTPS). Starting with version 23.3.02, port 80 and 443 are deprecated.
23.3.01
Collect incidents from Entuity by using the BMC Helix Intelligent Integrations SaaS deployment
Collect incidents from Entuity by using the BMC Helix Intelligent Integrations SaaS deployment, in addition to the BMC Helix Intelligent Integrationson-premises gateway.
For more information, see Integrating-with-Entuity.
Include additional parameters when configuring the Apache Kafka connector
Use the All properties field to specify any additional authentication parameters that are not available on the Source connection page. You can specify the parameters in the parameter=value format. For example, if you want to use the client DNS lookup parameter, you can specify client.dns.lookup=use_all_dns_ips in this field. To specify multiple parameters, use a comma-separated list.
For more information, see Integrating-with-Apache-Kafka.
23.3
Learn about the new features and enhancements in this release in the following video (1:50):
Collect data from Apache Kafka
Collect event and metric data from Apache Kafka.
For more information, see Integrating-with-Apache-Kafka.
Collect additional data from Catchpoint
Collect topology data, in addition to alerts and metrics, from Catchpoint.
For more information, see Integration with Catchpoint.
Collect alert data filtered by criticality, alert type, and alert sub type in VMWare vROps
Collect alert data for specific criticalities, alert types, and alert sub types in VMWare vROps.
For more information, see Integration with VMWare vROps.
Collect additional values of metric data points from Datadog
Collect the sum, average, and minimum values, in addition to the maximum value, of metric data points from Datadog by using the Time Aggregation option.
For more information, see Integrating-with-Datadog.
Collect data from additional third-party products
Collect metric and topology data from Entuity.
For more information, see Integrating-with-Entuity.
Collect events from Datadog.
For more information, see Integrating-with-Datadog.
Collect groups data from Microsoft SCOM
Collect data from specific groups in Microsoft SCOM by using the SCOMGroups option to select the groups.
For more information, see Integrating-with-Microsoft-SCOM .
