Best Practices for CMDB implementation.
- Enable CMDB Health dashboard:
by default the CMDB health dashboard jobs are disabled. Need to enable it manually.
It used to show the health indicators such as duplicate CIs , Required ci fields, and audit for overall health of CMDB.
Navigate>> CMDB view>> click on CMDB health dashboard Job >enable it.
- Utilize OOB CI classes as much as Possible.
Use OOB ci classes don’t try to create new . and it is also not best practice to extend off of CMDB_CI.
Ex: if you create the laptop table the extend with hardware table not CMDB_CI.
- CMDB Attribute should be placed at the right level.
Ex: BIOS_date attribute you want to create in window, Linux, Unix class instead you directly create in server class.
Use OOB attribute instead create new.
- You should not alter Relationships.
OOB Relationship you should not modify that.
- Try to use a tree Picker wherever Possible.
Use for location Attribute.
- Custom CMDB table Begin with “u_cmdb_ci….”
Ex: u_cmdb_ci_demo
- Application should have a Business owner assigned.
Check to see that a Business owner has been assigned to each business Application.
if this article helped you in any way then mark it helpful.
Thanks
