Troubleshooting data monitoring rules
When you create, run, or schedule a data monitoring rule, you might encounter some issues.
The following table provides the issue details and the resolutions:
| Issue symptom | Issue scope | Resolution |
|---|---|---|
| You cannot save a data monitoring rule. | Occurs when you try to create a data monitoring rule. | Verify that you have entered all the required fields in the New monitoring rule form. |
| You cannot save a criterion. | Occurs when you try to create a data monitoring rule. | Verify that you have entered the expression in the correct syntax. You will not be able to save a criterion until you enter the expression in the correct syntax. |
| You get no CI results for the data monitoring rule. | Occurs when the following conditions are true:
| The filter criteria might be too strict. Broaden the filter criteria to view CI results. |
| You cannot run a data monitoring job. | Occurs when you try to run a data monitoring rule. | Verify that the data monitoring rule is in Active status. You cannot run a rule with an Inactive status. |
| View results option is disabled in a data monitoring rule. | Occurs when you try to view the results of a data monitoring rule. | Verify that the data monitoring rule is in Active status. You cannot view the results of a rule with an Inactive status. |
| You cannot view insights into the data monitoring rule. | Occurs when you try to view an overall summary of the rule and its resolution suggestion. | Verify with your administrator that BMC Helix ITSM is integrated with BMC HelixGPT. Verify with your administrator that View Insights is enabled in BMC Helix Innovation Studio. |
| You cannot edit the Duplicate records rule. | Occurs when you try to modify the Duplicate records rule. | The Duplicate records rule is system-defined and cannot be modified. Only scheduling and enabling or disabling actions are supported. |
| The relationship-based rule does not return expected results. | Occurs when validating relationships between CIs. | Verify that the relationship exists directly between the selected Primary and Related classes. Multi-level relationships are not evaluated. |
| The previous reconciliation errors for configuration items (CIs) are overwritten and are no longer displayed in the CMDB:JobRunInfo form. | Occurs when a reconciliation job runs multiple times with the same configuration. The system retains only the latest reconciliation job details in the CMDB:JobRunInfo form. If the latest run has no failed CI, no entry will remain available in CMDB:JobRunInfo form. | To retain failed configuration items, create a new reconciliation job and set the 'allow-failed-CI flag' to 'True'. Run the job once and do not schedule it. The failed configuration items from that run remain available in the CMDB:JobRunInfo form for analysis. |
| You can see the Duplicate records rule in the console, but you cannot edit or run it. | Occurs when you try to edit or run the Duplicate records rule. | Verify that the Duplicate records rule is enabled. If the Duplicate Records rule is disabled, it remains visible in the Data Monitor console. You can view the rule, but cannot edit it, run it, or access its results. |
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*