25.1.00 enhancements and patches

Review the BMC Helix IT Operations Management (BMC Helix ITOM) enhancements made available in the 25.1.00 version for features that will benefit your organization.

Hotfixes in This Release

The following hotfixes are released on BMC Helix IT Operations Management OnPrem v25.1.00:

Hotfix	Details
25.1.00.004	Fixes an issue where zombie processes were generated in the Redis cluster pods.
25.1.00.002	Fixes an issue where incorrect API calls to the feature flag service continuously triggered TMS API calls.

To apply the hotfix when performing a fresh installation of v25.1.00, see Deploying BMC Helix IT Operations Management.
To apply the hotfix when upgrading from 24.4 to 25.1, see Upgrading BMC Helix IT Operations Management from version 24.4 to 25.1.
To apply the hotfix when upgrading from 24.3 to 25.1, see Upgrading BMC Helix IT Operations Management from version 25.3 to 25.1.

Updates in 25.1.00

Support Redis cluster

To improve stability and performance, BMC Helix ITOM supports Redis cluster for all application services, except BMC Helix Dashboards , which continues to use Redis-ha.

For more information, see _REDISCLUSTER in Configuration-file-settings.

Support integration with external logging solutions

You can now integrate BMC Helix ITOM with external logging systems - Splunk, and external Elasticsearch, Fluentbit, and Kibana (EFK) stacks.

For more information, see Preparing to collect logs from external log sources.

Scale down and scale up data lake components

During disaster recovery, BMC Helix ITOM has an option to scale down and scale up data lake components that are running.

To scale down both applications and data lake services, run ./product_scale.sh down-all. This stops all applications and services except MinIO, Postgres, and the PCS EFK installed to collect logs.

To scale up both applications and data lake services, run ./product_scale.sh up-all.

For more information, see:

Enable priority class for data lake and application services

To avoid critical data lake services from getting stuck because of resource unavailability, BMC Helix ITOM allows cluster admins to define priority during Kubernetes scheduling. This improves resource availability to the critical services, by assigning highest priority to the data lake services, over application services, Minio and other services.

For more information, see ENABLE_PRIORITY_CLASS_SUPPORT parameter in Configuration-file-settings.

Improved Container Security

The following infrastructure components are enhanced with container security by enabling the read-only root file system flag in the security context.

redis-cluster
redis-ha
Minio
Zookeeper
Kafka
Kafka-exporter
Victoria Metrics all components
OpenSearch Monitor jobs

What else changed in this release

The following table lists the changes in the product behavior in this release:

Update	Product behavior in versions earlier than 25.1	Product behavior in version 25.1
Moved efk-fluent-bit-clusterrole.yaml to the utilities folder The file is used for external EFK logging.	The efk-fluent-bit-clusterrole.yaml file was under helix-on-prem-deployment-manager /bmc-helix-logging /efk/fluent-bit /	The efk-fluent-bit-clusterrole.yaml file is moved to helix-on-prem-deployment-manager/ utilities/bmc-helix-logging/efk/fluent-bit/
Moved bmc-helix-logging.config to utilities folder. The file is used for external EFK logging.	The bmc-helix-logging.config file was under helix-on-prem-deployment-manager/configs/	The bmc-helix-logging.config file is moved to helix-on-prem-deployment-manager/utilities/bmc-helix-logging /
Moved the following parameters to bmc-helix-logging.config KIBANA_LB_HOST- The BMC Helix Logging Ingress uses the value of this parameter. ESLOG_MASTER_STORAGE_CLASS- a single storage class is configured for all the infra services by using block storage. ESLOG_DATA_STORAGE_CLASS-a single storage class is configured for all the infra services by using block storage.	The following parameters were part of infra.config KIBANA_LB_HOST ESLOG_MASTER_STORAGE_CLASS ESLOG_DATA_STORAGE_CLASS	The following parameters moved to bmc-helix-logging.config KIBANA_LB_HOST ESLOG_MASTER_STORAGE_CLASS ESLOG_DATA_STORAGE_CLASS
Moved KIBANA_PASSWORD parameter	Parameter was available in secret.txt file.	Moved the parameter to support external EFK logging.
Renamed INTELLI_INT_SERVICES parameter	The parameter was named INTELLI_INT_SERVICES and was used for Intelligent Integration (Stream Weaver) installation in the deployment.config file	The parameter is renamed to LOG_ANALYTICS_SERVICES to avoid confusion with the installation of Developer Tools and Log Analytics. For more information, see Configuration-file-settings .
Added REDIS_CLUSTER_STORAGE_CLASS parameter	Not present in the earlier versions.	Added new parameter REDIS_CLUSTER__STORAGE_CLASS in infra.config file to support specific configuration for Redis cluster storage class.
Added _REDISCLUSTER parameter	Not present in the earlier release.	Added new parameter _REDISCLUSTER in infra.config file to configure the Redis cluster.
Removed _REDIS parameter	Parameter was available in the deployment.config file.	Removed this parameter and introduced a new parameter _REDISCLUSTERfor clarity reflecting its use in Redis cluster configurations.
Removed BMC_HELIX_LOGGING parameter	Parameter was available in the deployment.config file.	Removed the parameter due to the deprecation of BMC Helix Logging integration.