Missing Discovery sources in CMDB 360

[abhijitjosh]

I have a lab instance for CMDB training. In the CMDb Workspace --> CMDB 360, the panel for Discovery sources is empty (picture below). Shouldn't it show at least 1 source, ServiceNow, for the pre-filled CIs in the system? 

[Dr Atul G- LNG]

Hi @abhijitjosh 

Enable and configure CMDB 360

• Activate the ITOM Discovery License (com.snc.itom.discovery.license) plugin.
• Navigate to All > Configuration > CMDB 360 Properties. Then, in the CMDB 360 Properties pane ensure that the glide.identification_engine.multisource_enabled (Enables CMDB 360) property is set to true.
• Optionally, Exclude classes from CMDB 360.

By default, CMDB 360 tracks discovery source information for CIs from CMDB classes and doesn't collect data for non-CMDB tables. You can independently enable or disable tracking data for CMDB and for non-CMDB classes, using these system properties: ​

• glide.identification_engine.multisource_cmdb_ci_enabled (Enables capturing CMDB 360 data for CIs from CMDB classes)​
• glide.identification_engine.multisource_non_cmdb_ci_enabled (Enables capturing CMDB 360 data for CIs from non-CMDB classes

[abhijitjosh]

Thanks Atul. ITOM Discovery plugin was enabled on the instance already. I enabled the .identification_engine.multisource_cmdb_ci_enabled property as well. Still no change.

[Dr Atul G- LNG]

Hi @abhijitjosh 

Since this is a lab instance, it must show the source.
Did you check whether there is any lab exercise available for this module?

https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/configuration-managem...

[Pratiksha]

Here is a clear, educational, and polished version of your statement with correct flow and terminology:

---

As suggested by Atul, you need to enable the required system property in order to see the data.

The key prerequisites for this to work are:

1. ITOM license
   You must have an active ITOM license, as this capability is part of ITOM functionality.

2. CI ingestion through IRE
   All Configuration Items (CIs) ingested into the CMDB must be processed through the Identification and Reconciliation Engine (IRE).
   CIs that bypass IRE (for example, manual inserts or custom scripts without proper IRE usage) will not be considered for this data.

Once these prerequisites are met and the property is enabled, the system will be able to calculate, track, and display the relevant CMDB data correctly.

This ensures consistency, avoids duplicate CIs, and allows CMDB health and governance mechanisms to function as intended.

Regards, 

Pratiksha