Issues table
Component | Description | Corrected in | Affected versions | Defect ID |
|---|---|---|---|---|
Health score | Symptom: When all the associated nodes are deleted, the health score of the service is updated to 100, but the impacting events count does not change. Scope: When all the associated nodes are deleted, the health score of the service is updated to 100. When the health score changes, the impacting event count should also be updated. | 24.3.00 | DR0F3-14393 | |
Health timeline | Symptom: The Health timeline and CI topology information is not displayed and the UI stops responding when the user groups are not associated with any authorization profile. Scope: When the user groups are not associated with any authorization profile, an error message should be displayed on the UI indicating that the issue is related to the permissions. The health timeline and CI topology information should displayed on the UI. | 24.3.00 | 23.4.02 | DR0F3-10116 |
Prediction events | Symptom: Prediction event is created with closed status and no policy is applied. Scope: Prediction events are created with status open when the predicted data point is violated for the configured threshold for the applied alarm policy, and when the event policy is applied. In prediction, there is a scheduled job that runs every 10 mins (default is 20 mins), for the configured health metrics. This job generates forecast data based on configured thresholds in alarm policy and it creates or closes the prediction event. In this case, prediction events are created with status open when the predicted data point is violated for the configured threshold for the applied alarm policy and when the event policy is applied. And prediction event is closed in the next scheduled job is run and few slots are missing, in this case, giving impression that the prediction is created with closed status and no policy is applied. | 24.3.00 | 24.2.01 | DR0F3-13171, DRTOM-36229 |
Incidents for situations | Symptom: The Situation is stabilized and no new events will be added now. message is not displayed for a situation event in the Logs and Notes tab in BMC Helix Operations Management. Scope: After a situation is stabilized based on the stabilization window, the message - Situation is stabilized and no new events will be added now is displayed in the Logs and Notes tab. However, if a primary and a similar situation are formed at the same time, sometimes this message is not displayed. This does not affect the behavior of the situation. | 24.2.01 | ||
Incidents for situations | Symptom: Related situations show incident ID, but no incident ID is displayed in the primary situation. Scope: If the incident is created for a situation after a primary situation is formed, then the primary situation does not show the incident ID. | 24.2.01 | DR0F3-12106 | |
Incidents for situations | Symptom: A single causal CI host name is displayed in the incident created for ML-based situations in BMC Helix ITSM. Scope: If a situation has multiple root cause events, the incident includes the CI details of only one of them. | 24.2.01 | <need a defect ID> | |
Situations > Similar Situations | Symptom: Not all closed situations are displayed in the group of similar situations. Scope: Situations that are closed manually before saturation are not considered for grouping. | 23.2.x | DR0F3-5219 |