CMDB Health Report
CMDB Health KPIs and metrics
The overall CMDB health score consists of three Key Performance Indicators (KPIs) which are correctness, compliance and completeness, each further consisting of sub-metrics. Each KPI and metric is associated with a scorecard that determines its contribution to the aggregated health at the overall CMDB level, class, and CI level.
You can configure which KPIs and metrics are included in the aggregated calculation, and set their weight in the aggregation. In the base system, all KPIs and all metrics are included in the aggregated health report.
Overall
An aggregation of all three KPIs (correctness, completeness and compliance), according to their overall scorecard weight settings.
Correctness
A KPI which is an aggregation of the following metrics, according to the correctness scorecard weight settings.
OrphanMeasures the percentage of orphan CIs in the CMDB. A CI can become orphan if it was unintentionally left in the CMDB when it is no longer needed. A CI is determined to be orphan if:The CI satisfies the criteria in an orphan rule. This criteria checks for specific attributes that a CI must have, and for CIs that have no relationships or that don't have specific relationships.Data is missing for the CI in its respective table, or in one of its parents' table.StalenessMeasures the percentage of stale CIs in the CMDB. A CI is stale if it was not updated within the Effective Duration time period that is specified in the staleness rule that applies to the class.The base system includes a default staleness rule for the Configuration Item [cmdb_ci] class, which sets the Effective Duration time to 60 days. This rule applies to all extended CMDB classes, and can be overridden by class specific staleness rules defined by the user. To determine CI staleness, a staleness rule for the CI's class is used if it exists, otherwise, the default staleness rule is used.In addition, a relationship in which a stale CI is a parent or a child, is determined to be a stale relationship.Note: Discovery marks VMware vCenter CIs that no longer physically exist, as stale. This setting takes precedence over a CMDB Health staleness rule defined for the CI. When drilling-down in the CMDB dashboard to Health Results, the Source for these CIs is CLOUD_DISCOVERY. For more information, see Discovery for VMware vCenterDuplicateMeasures the percentage of duplicate CIs in the CMDB using identification rules. Only independent CIs are evaluated for duplication. In a set of duplicate CIs, the count of duplicate CIs is the total number of CIs in the set, minus one. The detailed graphs for a duplicate set of CIs display all the CIs in the set.
Completeness
A KPI which is an aggregation of the following metrics, according to the completeness scorecard weight settings.
RequiredMeasures the percentage of CIs in which fields that are defined as mandatory, are not populated. Missing fields are tagged as incomplete noting that for this CI some information is missing. Required fields are equivalent to the fields that are specified as mandatory in the system dictionary.RecommendedMeasures the percentage of CIs in which fields that are set as recommended, are not populated. Out-of-box, no recommended fields are specified.
Compliance
Based on the results of actual CMDB audit runs.
AuditAudit compares actual values of specified fields, against expected values defined in template and scripted audits. Based on the Last run date of audits, CMDB Health identifies the set of the most recent complete audit run, and uses those audit results. To pass the CMDB Health audit test, a CI must be in compliance with all audits for that CI. Create a compliance-type audit, for which the results are calculated into the CMDB Health compliance KPI.When running scripted audits, the Last run date is not populated. Therefore, for the compliance KPI to include the results of a scripted audit, update the script in the audit to record the audit run time.For more information, see Create an audit.
Relationships
Measures the health of CI relationships, consisting of the following metrics which are not-configurable:
Duplicate relationshipsRelationships that have identical parent and child CIs, identical relationship type, and an identical port. Duplicate relationships are displayed per relationship type. In a set of duplicate relationships, the duplicate relationship count is the total number of duplicate relationships in the set, minus one. The detailed graphs for a duplicate set of relationships display all the relationships in the set.Orphan relationshipsA relationship that is missing either a parent CI, a child CI, or both.
Stale relationshipsA relationship in which the parent CI or the child CI is a stale CI.
A single relationship can fail more than one health test. For example, a duplicate relationship can also be stale.
- Relations not compliant with suggested relations
- Relations not compliant with containment rules
- Relations not compliant with hosting rules
Configure CMDB groups scorecard thresholds
Each CMDB group can have its unique set of scorecard thresholds for best, at risk, and critical state definitions for specific KPIs or metrics.
Before you begin
Role required: itil_admin (on top of itil)
About this task
- 0 - lower threshold: Best state
- Lower threshold - upper threshold: At risk state
- Upper threshold - 100: Critical state
CMDB groups scorecard thresholds are stored in the [cmdb_health_scorecard_group_threshold] table.
Procedure
Create health inclusion rule
You can narrow the scope of CIs that are included in health calculations by defining health inclusion rules. Health inclusion rules can be specified per domain.
Before you begin
Role required: itil has read access, itil_admin (on top of itil) has full access.
About this task
Evaluation for the required, orphan, recommended, and staleness health metrics, will apply only to CIs that satisfy health inclusion rules. For the duplicate metric, Identification inclusion rules can be used for that purpose.
In the base system, there are no predefined health inclusion rules, in which case all CIs are included in the CMDB Health calculations.
Procedure
Enable and configure a CMDB Health Dashboard job
Enable and configure the jobs that process CMDB health tests, to start calculating CMDB health scores for the completeness, compliance, correctness, and relationship KPI. These health scores are then aggregated into the overall CMDB health report.
Before you begin
Role required: admin
About this task
In the base system, CMDB Health Dashboard jobs are disabled by default. Enable and configure the respective job for the CMDB health KPI that you want data collected and aggregated for. You can schedule a job to run on a recurring schedule, or execute it once at any time.
Procedure
Result
After you enable a CMDB Health Dashboard job, the results for the KPI are aggregated and displayed in the CMDB dashboard and CI dashboard, at the CMDB, class, and CI levels.
CMDB QUERY
Build a CMDB query using the CMDB Query Builder
LondonA CMDB query type queries the infrastructure for CI classes and the relationships and references that connect them.
Role required: cmdb_query_builder (contained for itil and asset)
Build the query by dragging the CI classes that you want to include in the query, dropping them as nodes on the canvas, and then defining relationship properties between them. For every class node in the query, you can filter on its attributes to narrow down the results to a specific set of CIs of that class or to a single specific CI. You can also select the property columns that display in the query results. Query filters use related list conditions which allow the inclusion of a relationship with another table in the filter. For more information, see Add related list conditions.
Authorized users can update and delete a query created by another user.
Procedure
What to do next
Click Save.
In the Saved Queries tab, you can point to a saved query widget and click the 'i' icon to view query information such as the query type, last update date, CMDB groups associated with the query, and the query schedules.
- Click Run.Note: When a query is running, wait for it to complete or to time out before opening or running another query.
The query results pane displays only the first 100 results of the query.
- Click Load More Results to display the next set of 100 results.
- Click Load All Results to display the rest of the query results, up to the number specified by the glide.cmdb.query.max_results_limit system property (10,000 by default).
- Create a report from CMDB query results.
- Create a schedule to run the query at a future time, and to email the results to interested parties.
Click the Query Results context menu and select Export. Even if the Load More Results button is visible, indicating that there are additional query results, only the results that are visible are exported.
- Populate a CMDB group using the saved query.
Open Questions
Question | Answer | Date Answered |
---|---|---|