What is CMDB Health? Check out ServiceNow Doc page CMDB Health to find out.
In this post, I am going to setup the CMDB View to filter down the scope of CI classes and to track the following items:
- Check missing Serial numbers for all Hardware CIs
- Check for all Hardware Stale CIs
- Check for missing model entries for hardware CIs
- Check for missing service ownership for services
- Check for CIs without names
First we want to setup "health inclusion rules". These rules will define which CI classes we will run the health metrics against. Also, allows us to filter out the noise(supporting CI classes). Before moving forward, please read more about "Health inclusion rules" to understand what I am sharing below with examples.
Example setup for metrics: Required and Recommended (Mod to meet client needs)
Example setup for metrics: Orphan, Staleness and Duplicate (Mod to meet client needs)
With these health inclusion rules in place, we are filtering only on CIs that extend from cmdb_ci_hardware and cmdb_ci_service tables that met the status conduction.
Time to setup recommended fields at the cmdb_ci_hardware class to track the following health checks:
- CIs without name
- CIs with meeting model entries
- CIs with missing serial numbers
Setup recommended field(s) at cmdb_ci_service class to track the following health check:
- Missing Service ownship
After above changes, you are enable or rerun CMDB health Dashboard Jobs:
Follow steps via doc link Enable and configure a CMDB Health Dashboard job to setup jobs.
Tip: Setup jobs to run after you have data sources updating CMDB to see most up to date results.
Please hit the "Helpful" button below if you find this helpful and share with others. Also, leave a comment if this example of setup helped out or if you have other examples to share.
