CMDB Health process status: failure threshold reached
The CMDB dashboard displays the string ‘failure threshold reached' when the number of CIs that are failing the metric tests, reaches the failure threshold set for the metric.
CMDB Health stops processing for this metric in the current cycle, and therefore there is no aggregated health score for the metric. Processing will be attempted again in the next cycle. Also, status in the CMDB Health Metric Status [cmdb_health_metric_status] table is set to Max Failures for this metric.
When the health score of a metric cannot be evaluated, then the processing status of the respective KPI (for example, correctness) is set to Incomplete. The CMDB dashboard displays the string Incomplete score for the respective KPI and for the CMDB Health overall score. Also, aggregated health scores for the metric are not available for any class in the CMDB hierarchy.
- Review and refine the rules defined for the metric which has reached max failures. If a rule associated with the metric is too generic, resulting in large number of failures, attempt to refine it as follows:
Completeness:
Review the mandatory fields for the associated classes and remove those that aren't critical for the health score. Also, review the recommended fields that are causing failures and remove those that aren't critical for the health score.
For more information see Set a CI attribute to be mandatory and Set a CI field to be recommended.
Compliance:
Review the audit failures from the audit jobs and adjust the audits to reduce the number of failures. For more information, see CMDB Health KPIs and metrics.
Correctness:
- Orphan: Review the orphan rules and adjust them to remove excessive orphan failures. For more information, see Create or edit a CMDB Health orphan rule.
- Staleness: Review the effective duration for the classes that are causing failures and adjust the duration to reduce the number of failures. For more information, see Create or edit a CMDB Health staleness rule.
- Duplicate: Review the de-duplication tasks and remediate the tasks to remove duplicate CIs and to avoid creating failure records. For more information, see Remediate a de-duplication task (legacy).
- Increase the failure threshold for the metric that is failing and check if processing for this metric completes successfully in the next cycle. Increasing the failure threshold beyond 500K might reduce overall performance.