CMDB Workspace Inaccuracy

FriendlyDude
Tera Contributor

Hello,

 

I was checking out CMDB 360 in workspace and I can see there that "Total CMDB 360 Records" is having 17 million records.

 

Screenshot 2025-07-28 191841.png

 

However, when I checked the cmdb_ci table it is fetching 24 million records.

 

Screenshot 2025-07-28 191953.png

 

How can this be fixed?

1 ACCEPTED SOLUTION

AJ-TechTrek
Giga Sage
Giga Sage

Hi @FriendlyDude ,

 

As per my understanding, You can follow the below step, I hope this will help.

 

This is Great question and this difference is expected in ServiceNow due to how CMDB 360 works.
Here’s why you see 17 million records in CMDB 360 vs 24 million in cmdb_ci:

 

2. Explanation:
* cmdb_ci table:
Contains all configuration items (CIs), including:
* Active & inactive / installed, retired, disposed
* Duplicates
* Orphaned CIs
* Non-managed or irrelevant CIs
* This raw count (24 million) is the total number of rows.
* CMDB 360 (Total CMDB 360 Records):
* CMDB 360 uses Data Foundations, Data Certification, and Data Manager policies to only include:
* In-scope CIs
* Managed CIs (Install status = Installed / In production, not Retired/Disposed)
* CIs matching specific cmdb_data_source or compliance criteria
* Excludes:
* Retired, disposed, obsolete CIs
* Possibly CIs from non-managed classes (like snapshot classes, temp tables, etc.)

 

2. So why fewer records?


CMDB 360 deliberately focuses on the subset of CIs considered:
* In scope
* Managed
* Tracked for completeness, correctness, compliance, staleness
It is not designed to show the full raw count.

 

3. What to do next:


 

If you want to reconcile the numbers:
1. Check your CMDB 360 scope settings:
* Open CMDB 360 Configuration → see which classes, install statuses, and data sources are included.


2. Run a report:
SELECT COUNT(*)
 FROM cmdb_ci
 WHERE install_status = '1' -- Installed/In use
AND sys_class_name IN ([managed classes])


Compare this number to CMDB 360.


3. Review CMDB Data Foundations > Data Manager policies:

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj

Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

View solution in original post

3 REPLIES 3

Dr Atul G- LNG
Tera Patron
Tera Patron

Hi @FriendlyDude 

I’m not 100% sure, but please check the CMDB table to see if it’s showing all the source data.
Because in the 360 view, it displays data from all sources.

*************************************************************************************************************
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.

Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]

****************************************************************************************************************

AJ-TechTrek
Giga Sage
Giga Sage

Hi @FriendlyDude ,

 

As per my understanding, You can follow the below step, I hope this will help.

 

This is Great question and this difference is expected in ServiceNow due to how CMDB 360 works.
Here’s why you see 17 million records in CMDB 360 vs 24 million in cmdb_ci:

 

2. Explanation:
* cmdb_ci table:
Contains all configuration items (CIs), including:
* Active & inactive / installed, retired, disposed
* Duplicates
* Orphaned CIs
* Non-managed or irrelevant CIs
* This raw count (24 million) is the total number of rows.
* CMDB 360 (Total CMDB 360 Records):
* CMDB 360 uses Data Foundations, Data Certification, and Data Manager policies to only include:
* In-scope CIs
* Managed CIs (Install status = Installed / In production, not Retired/Disposed)
* CIs matching specific cmdb_data_source or compliance criteria
* Excludes:
* Retired, disposed, obsolete CIs
* Possibly CIs from non-managed classes (like snapshot classes, temp tables, etc.)

 

2. So why fewer records?


CMDB 360 deliberately focuses on the subset of CIs considered:
* In scope
* Managed
* Tracked for completeness, correctness, compliance, staleness
It is not designed to show the full raw count.

 

3. What to do next:


 

If you want to reconcile the numbers:
1. Check your CMDB 360 scope settings:
* Open CMDB 360 Configuration → see which classes, install statuses, and data sources are included.


2. Run a report:
SELECT COUNT(*)
 FROM cmdb_ci
 WHERE install_status = '1' -- Installed/In use
AND sys_class_name IN ([managed classes])


Compare this number to CMDB 360.


3. Review CMDB Data Foundations > Data Manager policies:

 

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 
Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj

Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025

This is very helpful information, thanks!