Issues tables

Symptom: The Reporter system task displays a higher number of failed Helix Dashboard reports than the actual failed reports.

Scope: When running a large number of reports (for example, 600-700), and each report size is greater than 11 MB. 

Symptom: The Entity cleaner task causes the service optdataorg to fail with the out of memory error. 

Scope: When you have a large number of entities to be deleted. 

Workspace

Open

DR0AV-15209

Capacity Views

Open

DR0AV-16015

Benchmark

Open

DR0AV-16771

Symptom: In the Kubernetes recommendations for Overallocated Containers, the reclaimable CPU calculation did not consider the number of pod replicas, leading to an underestimation of total reclaimable CPU in workloads with multiple pods.

Symptom: Clicking on entities from search results caused errors.

Scope: When the searched entity is associated with inactive domains.

Symptom: In the Kubernetes > Controllers> Controller details page, after you access any of the Pods of the Controller pages from the Related Information panel, the pod details pages are incorrect and have missing image links. 

Symptom: When calculating the days to saturation indicator for a Kubernetes cluster, the sizing values were inconsistent in cases where clusters are scaled down or turned off during weekends or low-usage periods.

Symptom: In the Kubernetes > Clusters view, the memory and capacity tabs used outdated metrics, leading to an inaccurate representation of memory utilization.

Symptom: The Nutanix ETL run failed with error BCO_ETL_ERR011 due to a null pointer exception when attempting to retrieve the CPU frequency of a Nutanix host.

Scope: When you ran your Nutanix ETL in a setup where the host's CPU frequency data was missing or not reported.

Symptom: In the Queueing Network Model, values in the Current value column of the Business Drivers table were calculated by using the hourly sum statistic of all metrics rather than the default statistic for each metric.

Symptom: The configuration metrics were not getting recomputed correctly for a few derived systems and displayed errors.

Scope: When these derived systems are migrated from TrueSight Capacity Optimization to BMC Helix Continuous Optimization. 

Symptom: Entity Catalog names did not match the corresponding system entity names, causing inconsistencies during reconciliation.

Scope: When you run the VMware ETL with the Import advanced VM events setting enabled, system names remained accurate, but the Entity Catalog was not updated, leading to mismatches.

Symptom: ​​​When migrating entity filters from TrueSight Continuous Optimization to BMC Helix Continuous Optimization, filters containing the lowercase logical operator AND failed to retrieve results.

ETL

Fixed in 25.2.00

DR0AV-16422

Symptoms: The Data sender task did not parse the configuration metric value successfully.

Scope: When the metric value contained statistic and one of the statistic contains a letter 'e' in small case. 

DR0AV-20952

DR0AV-20926

Symptoms: The Data migrator ETL run failed.

Scope: When the task runs more than the expected time (4 hours), but sending the email fails. 

DR0AV-20889

Symptoms: In the Servers Overview view > File Systems page, the File System Size [GB] column was empty for the Windows data. 

DR0AV-20838

Symptoms: The tagging rule manager system task failed.

Scope: When the tagging rule was running for more than 300 entities.  

DR0AV-20786

DR0AV-19707

Symptom: Summary data mart converted numbers stored as text to a numeric data type.

Scope: When you used the custom metric (whose value is stored as text) in the summary data mart. 

DR0AV-21173

Symptom: In the Pods page of the Kubernetes view, the CPU Bottleneck Indicator values were displayed incorrectly.

DR0AV-21147

Symptom: In the Collect Logs output of the systems, logs and errors generated after the 10K lines were not visible in the logs, as the logs were truncated to 10K lines.   

DR0AV-20927

Symptom: While searching for certain systems in Workspace, the following error was displayed: 

getting wrong url - value [undefined]

Scope: When these systems are children of the deleted domains.

DR0AV-20892

DR0AV-20689

Fixed in 25.2.00

DR0AV-19108