Issues tables
Review the following table for issues that were corrected in BMC Helix Operations Management and for known issues that remain open.
| Corrected issues | View the issues in the following table by the default sort order, Corrected in, which shows the corrected issues first. The version number represents the update (Year-Month-Day) in which the issue is fixed. |
|---|---|
| Known (open) issues | To view only the open issues, click the Corrected in filter, and select empty. An issue without a value for Corrected in remains open. |
You can also filter and sort issues according to component or defect ID.
Known and corrected product issues
Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.
The table is being loaded. Please wait for a bit ...
| Component | Description | Corrected in | Defect ID |
|---|---|---|---|
| Events | If the following API endpoint returns approximately more than 1025 event IDs, the API does not work as expected despite a successful response.https://<BMC Helix Portal URL>/events-service/api/v1.0/events/operations/close | 2021-11-29 | DRTOM-18979 |
| Events | When you use the following functions in an advanced enrichment policy, incoming events are dropped when you modify a note or add a blank note in the event.
| 2021-11-24 | DRTOM-19204 |
| Event policies | De-duplication of events using the lookup action in advanced enrichment policies fail during an event burst resulting in an incorrect count for the _repeat_count event slot. | 2021-11-23 | DRTOM-19107 |
| Events | If an aggregated event closes within the time window, new matching events are correlated to the closed aggregated event. | 2021-10-07 | DRTOM-18487 |
| Event policies | In the advanced enrichment and time-based enrichment policies, the following issues occur: Symptom: In the policy workflow area, the action tooltips get partially hidden behind the preceding action element. Scope: The label specified for the action is very long, for example, more than 100 characters. Workaround: Avoid adding labels that are longer than 100 characters. Symptom: In the policy workflow area, the action menu under Else gets hidden behind the succeeding action element added in the policy. Scope: You add the If-Then-Else action. Workaround: Instead of using the action menu for the Else action, add actions by using the actions toolbar at the top. | 2021-07-14 | DRTOM-15235 |
| Logs | Log ingestion hangs intermittently. | 2021-05-27 | DRE21-7130 |
| Events | Sending an event fails if the event does not contain the class slot, or contains the slot name in uppercase characters (CLASS). | 2020-04-27 | DRTOM-13805 |
| Alarm policies | While creating an alarm policy, the following issue occurs sometimes: Symptom: The alarm policy creation fails with a Workaround: Click Save again to save the alarm policy. | DRTOM-16316 | |
| Baselines | If an agent gets restarted, the earlier historical baseline data is lost and baseline is recalculated. | DRTOM-17077 | |
| Agents | If a restricted user runs a query on a PATROL Agent, a blank screen is displayed after the user logs in to the Configuration > Agents > Query PATROL Agent page. | DRTOM-18631 | |
| Performance Overview graph | If an alarm is closed, the alarm closure is not indicated on the Performance Overview graph. This happens only for the non-BMC monitor types. | DRTOM-17813 | |
| Service Monitoring Probable Cause Analysis | Symptom: Probable Cause Analysis is showing no data available. Scope: When you select a time slot on the health summary time frame for which there was an event that got closed in less than five minutes, the Probable Cause Analysis is showing no data available. However, it must show the causal nodes and events at that point. Workaround: There is no workaround. | DR0F3-290 |
Related issues
The following links provide information about issues in the integrated BMC Helix products.
Comments
Log in or register to comment.