Components installed with CMDB Health
Summarize
Summary of Components installed with CMDB Health
The CMDB Health application (part of thecom.snc.cmdbplugin) installs several essential components including tables, system properties, and scheduled jobs. These components work together to monitor and maintain the health of your CMDB by tracking key performance indicators (KPIs) related to completeness, compliance, correctness, and relationships within your configuration items (CIs).
Show less
Key Features
- System Properties: Includes properties like
glide.cmdb.serviceshierarchylimit, which controls the maximum number of service CIs shown on the CMDB service dashboard (default 10,000, range 0-100,000). This helps manage dashboard performance and data scope. - Scheduled Jobs: Multiple scripts run regularly to calculate KPIs for CMDB health:
- Completeness Score Calculation
- Compliance Score Calculation
- Correctness Score Calculation
- Relationship Score Calculation
- Relationship Compliance Processing (validates suggested relationships, hosting, and containment rules)
- Management of recommended identifier fields in rules for accuracy in health evaluations
- Tables: Several tables store configuration and results related to CMDB health metrics:
- CMDB Health Metric [cmdbhealthmetric]: Holds settings for KPIs and metrics, such as enablement and failure thresholds.
- CMDB Health Result [cmdbhealthresult]: Stores results from the latest CMDB health processing cycle.
- CMDB Health Scorecard [cmdbhealthscorecard]: Maintains current and historical health scores with status indicators.
- CMDB Health Orphan Rule [cmdbhealthorphanrule]: Defines rules for identifying orphan records by class.
- CMDB Recommended Fields [cmdbrecommendedfields]: Lists recommended fields per CI class to support completeness and compliance.
- Metric and Processor Status Tables: Track processing progress, statuses, and timing for KPIs and metric calculations, ensuring reliable and timely health assessments.
- CMDB Relationship All Rules Health Results [cmdbhealthresultrelall]: Stores relationship health data used in comprehensive relationship reports.
Practical Benefits for ServiceNow Customers
By leveraging these installed components, ServiceNow customers can expect:
- Automated, scheduled evaluation of CMDB health metrics for proactive monitoring.
- Visibility into detailed health scores and trends, enabling data-driven decisions to improve CMDB quality.
- Control over dashboard scope and performance via configurable system properties.
- Robust tracking and reporting on CI relationships and orphan records, which are critical for accurate service mapping and impact analysis.
- Streamlined management of recommended fields and identification rules, enhancing completeness and correctness of CMDB data.
Several types of components are installed with CMDB Health (included in the com.snc.cmdb plugin), such as tables, properties, and scheduled jobs.
Properties installed
| Property | Description |
|---|---|
| glide.cmdb.services_hierarchy_limit | Maximum number of service CIs that can appear in the CMDB service dashboard. This limit applies to any child class of the Service Instance [cmdb_ci_service_auto] class.
|
Scheduled jobs installed
| Scheduled job | Description |
|---|---|
| CMDB Health Dashboard - Completeness Score Calculation | Script for calculating the completeness KPI of CMDB health. |
| CMDB Health Dashboard - Compliance Score Calculation | Script for calculating the compliance KPI of CMDB health. |
| CMDB Health Dashboard - Correctness Score Calculation | Script for calculating the correctness KPI of CMDB health. |
| CMDB Health Dashboard - Relationship Score Calculation | Script for calculating the CI relationships KPI of CMDB health. |
| CMDB Health Dashboard - Relationship Compliance Processor | Script for calculating compliance of relationships with suggested relationships, and with hosting and containment rules. |
| Add Identifier Fields In Recommended Rules | Sets all criterion attributes from all active identifier entries from all active identification rules, as recommended fields. These added recommended fields are then checked by the CMDB Health Dashboard - Completeness Score Calculation scheduled job when evaluating the recommended health metric. |
| Remove Identifier Fields In Recommended Rules | Identifies any recommended field that is a criterion attribute in any active identifier entry in any active identification rule. Then removes the recommended setting for that field. |
Tables installed
| Table | Description |
|---|---|
| CMDB Health Metric [cmdb_health_metric] |
Details such as if a KPI or metric is enabled, maximum failure threshold, and other settings for all CMDB Health KPIs and metrics. |
| CMDB Health Result [cmdb_health_result] |
Results from the most recent CMDB Health processing cycle. |
| CMDB Health Scorecard [cmdb_health_scorecard] |
Current and historic health scores. Status of historic score records is 'Historic', and of latest score records is 'Complete’. |
| CMDB Health Orphan Rule [cmdb_health_orphan_rule] |
Rules for calculating orphan records per class. |
| CMDB Recommended Fields [cmdb_recommended_fields] |
Recommended fields per class. |
| CMDB Health Metric Status [cmdb_health_metric_status] |
Internal table that tracks the status of each KPI and metric that is being
processed. Includes status, processing time, and processing start date. State for
a KPI or metric changes from 'In Progress' to either of: Processing of a timed out KPI or metric continues on the following
day.
|
| CMDB Health Processor Status [cmdb_health_processor_status] |
Internal table that tracks the processing progress of each KPI and metric. Contains a list of tables that are processed for each KPI and metric, and processing status. Classes are processed sequentially, changing status from Draft -> In Progress -> Complete. |
| CMDB Relationship All Rules Health Results [cmdb_health_result_rel_all] |
Stores results about relationship health, to be used by the All Relationships report. |