{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":46776,"path":"servicenow-platform/configuration-management-database-cmdb/c_CMDBHealthTroubleshooting.md","title":"CMDB Health process tracking and troubleshooting","bundle":null,"doc_type":null,"release":"australia","body":"\n# CMDB Health process tracking and troubleshooting\n\nUse the following information to track and resolve issues with the CMDB Health processes.\n\n## Logging\n\nBy default, only error messages are logged to the syslog table, with the source name CmdbHealth. To enable logging of 'info' and 'warning' messages \\(which are typically logged at the start and end of each processing cycle\\), update the system property glide.cmdb.logger.use\\_syslog.CMDBHealth. For information about using this property, see [CMDB Health system properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/r_CMDBHealthProperties.md).\n\n## Processing status\n\nIf scheduled jobs are enabled, but data is not displaying on the <ph keyref=\"var.config-mgmt-database-short\"/> dashboard, you can check the processing status in the CMDB Health Metric Status \\[cmdb\\_health\\_metric\\_status\\] table. Depending on the status of the **inactive** metric, decide how to proceed.\n\nInitially, the state of all metrics is 'In Progress'.\n\nPossible final states of a metric:\n\n-   **Complete**\n\n    All classes are processed and the number of failures is under the maximum failures threshold.\n\n-   **Max Failures**\n\n    The number of failures for this metric reached the maximum failures threshold. Processing has been aborted and will start over in the next run.\n\n-   **Daily Time Out Pause**\n\n    The processor reached the processing time limit. Processing is paused and will resume in the next run.\n\n\nAt the end of a processing cycle, the final state of a KPI depends on the final state of its associated metrics. Possible final state of a KPI:\n\n-   **Complete**\n\n    All associated metrics are in Complete state and score calculation is complete.\n\n-   **Incomplete**\n\n    Score is not calculated because one of the associated metrics reached its maximum failure thresholds.\n\n-   **Daily Time Out Pause**\n\n    Timed out because one of the associated metrics has reached its processing time limit.\n\n\n## Processing time\n\nIf processing of a metric times out, you can find out which class takes too long to process. Use this information to find out if any validation rules are weak.\n\nThe progress of each metric is tracked in the CMDB Health Processor Status table \\[cmdb\\_health\\_processor\\_status\\]. Status for classes that have been processed for a metric is Complete, and for classes that are yet to be processed is Draft. By looking at the update time for each class, you can calculate the length of processing time for each class.\n\n## Orphan records due to broken hierarchy\n\nOrphan rules might detect an orphan CI, which you are not able to access and delete. Or, there might be a mismatch between the list view that displays the orphan records, and the total number of records. These findings are due to records being deleted in the database from only one table in the CMDB hierarchy.\n\nThese CI records are not accessible via GlideRecord and must be deleted directly from the database. Therefore, in this case, to delete an orphan CI from the database you must contact Support to get help.\n\nOrphan test results provide the details of where exactly the hierarchy is broken. For example, the message \"This cmdb\\_ci\\_linux\\_server CI \\[91054fc24f22520053d6e1d18110c713\\] is missing record in cmdb\\_ci\\_computer table\" means that a record of that sys\\_id must be deleted from the CMDB, cmdb\\_ci, cmdb\\_ci\\_hardware, cmdb\\_ci\\_server, and the cmdb\\_ci\\_linux\\_server tables \\(the Computer class is between the Hardware and the Server classes in the hierarchy.\\)\n\n## Scripted audits Skipped\n\nAn error message is logged if the results from a scripted audit are not included in the compliance KPI. The reason can be that the script in the audit was not updated to populate its **Last ran date** field. Without a **Last ran date** value, CMDB Health is unable to identify these run results as part of a recent complete audit run, and skips those results.\n\n-   **[CMDB Health process status: failure threshold reached](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/failure-threshold-reached.md)**  \nThe CMDB Health Dashboard shows the string ‘failure threshold reached' when the number of CIs that are failing the metric tests, reaches the failure threshold set for the metric.\n-   **[CMDB Health process status: incomplete score](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/incomplete-score.md)**  \nThe CMDB Health Dashboard shows the string 'incomplete score' for a metric when it fails to calculate the score for the metric.\n\n**Parent Topic:**[CMDB Health](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/c_CMDBHealth.md)\n\n**Related topics**  \n\n\n[Exploring CMDB Health]()\n\n[CMDB Health experience in CMDB Workspace and in Service Graph Workspace]()\n\n[View CMDB Health Dashboard]()\n\n[View relationships health]()\n\n[View CI health]()\n\n[Create a CMDB remediation rule]()\n\n[CMDB Health reference]()\n\n"}}