---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# CMDB 360

# CMDB 360 {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of CMDB 360

CMDB 360 is an advanced feature in ServiceNow that retains comprehensive historical data about discovery sources and their proposed values for Configuration Item (CI) attributes.
It enhances visibility into how the CMDB is populated by multiple discovery sources at the attribute level, enabling ServiceNow customers to track, revert, or recompute CI attribute updates efficiently.
CMDB 360 supersedes the legacy Multisource CMDB feature by offering additional capabilities such as an analytics dashboard and enhanced query functionality, accessible within the CMDB Workspace.
Show full answer Show less  

## How CMDB 360 Works

When multiple discovery sources update the same CI attribute, the Identification and Reconciliation Engine (IRE) applies reconciliation rules to determine which source's value is accepted. Unlike previous behavior where rejected discovery source data was discarded, CMDB 360 retains raw data for all discovery sources and CI combinations, regardless of whether their values were selected. This comprehensive data is stored in the **CMDB MultiSource Data \[cmdbmultisourcedata\]** table, which can be queried and reported on. Customers can choose to exclude specific classes or their descendants from CMDB 360 data collection if desired.

## Key Capabilities

* Create and manage dynamic reconciliation rules to control CI attribute updates by discovery source.
* Visualize the sources of attribute values at the attribute level for better data transparency.
* Revert updates from unreliable discovery sources and recompute attribute values excluding those sources.
* Validate new discovery sources by comparing their data to trusted sources.
* Query CMDB 360 data using the built-in query builder in CMDB Workspace or Service Graph Workspace to improve data quality and operational insights.
* Supports non-CMDB tables, extending visibility beyond traditional Configuration Items.

## Enabling and Configuring CMDB 360

* Activate the ITOM Discovery License plugin.
* Enable CMDB 360 by setting the system property **glide.identificationengine.multisourceenabled** to true in the CMDB 360 Properties.
* Optionally exclude classes from CMDB 360 data collection.
* Configure tracking for CMDB and non-CMDB classes independently using properties **glide.identificationengine.multisourcecmdbcienabled** and **glide.identificationengine.multisourcenoncmdbcienabled**.

## Reporting and Visualization

Use the CMDB 360 insights dashboard within CMDB Workspace to generate reports that help you:

* Identify CIs not reported by any discovery source.
* Discover which sources contribute data to your CMDB.
* Compare attribute values across different discovery sources or between the CMDB and discovery sources.
* Filter reports by application service, technical service, or CMDB groups for focused analysis.

CMDB 360 also integrates into the user interface, allowing users to preview reconciliation rules and see attribute-level source data directly on CI forms.

## Logging

Enable CMDB 360 logging by configuring the system property **glide.cmdb.logger.source.cmdbmultisource** . Logs can then be reviewed in the **Log \[syslog\]** table filtering by the source "cmdbmultisource" to monitor CMDB 360 activity.  
CMDB 360 retains complete history about discovery sources and proposed values, involved
in updates of CI attributes. Use CMDB 360 data to track how the CMDB is populated by various
discovery sources at the CI attribute level. Also, to revert CI updates from a specific
discovery source, or to recompute attribute values using updated reconciliation
rules.

CMDB 360 provides all the functionality of the legacy Multisource CMDB feature with additional capabilities such as an analytics dashboard, and new query functionality. You can access all of the CMDB 360 capabilities in the [CMDB 360 view in CMDB Workspace](https://www.servicenow.com/docs/iVzIajEAkKfltaKJctYJNg "The CMDB 360 view in CMDB Workspace and in Service Graph Workspace provides aggregations and analysis of CMDB 360 data which you can use to track activities and identify Potential issues of discovery sources. You can also create different types of your own queries and associated schedules and reports to explore CMDB data.") or in the [CMDB 360 insights dashboard in CMDB Workspace](https://www.servicenow.com/docs/h87uoAgsgd6ImEPk0UCk~Q "The CMDB 360 insights dashboard provides aggregations and analysis of CMDB 360 data, where you can track activities and identify potential issues of discovery sources.").

## How CMDB 360 works {#multisource-cmdb__section_glt_v4r_qlb}

When multiple discovery sources attempt to update the same CI attribute, the [Identification and Reconciliation Engine
(IRE)](https://www.servicenow.com/docs/sqNNkz3TEuCg6mpfcBg4OA "The Identification and Reconciliation module provides a centralized framework for identifying and reconciling data from different data sources. It helps maintain the integrity of the CMDB and some non-CMDB tables when multiple data sources are used to create and update CI records.") uses reconciliation rules to select a single discovery source for the update.
Without CMDB 360, details about the lower-priority discovery sources whose values were
rejected, are discarded. Also, it is difficult to identify the source of an attribute value
without CMDB 360.

With CMDB 360, the raw details for every discovery source and CI combination are retained for
both, discovery sources that were selected for an update and all others that were not. CMDB
360 data, consisting of records for each discovery source and CI combination, is stored in
the CMDB MultiSource Data \[cmdb_multisource_data\] table. You can examine, query, and report
on the CMDB 360 data store.

You can optionally exclude classes and their descendents from collecting and processing CMDB 360 data. The CMDB MultiSource Data \[cmdb_multisource_data\] table doesn't contain data for those excluded classes. For more
information, see [Exclude classes from CMDB 360](https://www.servicenow.com/docs/OpYiOMGe26JXQ~pFcMWw0Q "Prevent CMDB 360 from collecting, storing, and analyzing data for classes for which it isn't needed. CMDB 360 processes large amounts of data. Therefore, excluding classes can help improve the performance of the Multisource Dashboard Analytics Population scheduled job and of CMDB 360 queries.").  
Note:  
CMDB 360 supports non-CMDB tables. The widely used term Configuration Item (CI), can also refer to a non-CMDB table record. For information about support for non-CMDB tables, see [IRE support for non-CMDB tables](https://www.servicenow.com/docs/OpZo_hrWBt33DNrx6ZoFsQ "Apply Identification and Reconciliation Engine (IRE) processes to supported non-CMDB tables to ensure data integrity and health of those tables.").  
Figure 1. CMDB 360 insights into data source processes

After data is initially ingested from multiple data sources, several processes are applied to standardize and reconcile the data before it is stored in the CMDB. CMDB 360 provides insights that can help you configure some of
these processes.

## Using CMDB 360 {#multisource-cmdb__section_rpn_ywl_2tb}

Use CMDB 360 to:

* [Create a dynamic reconciliation rule](https://www.servicenow.com/docs/0pT4QlDmKokSjVO3j6FBJw#create-dynamic-reconciliation-rule "A dynamic reconciliation rule uses CMDB 360 data to choose a value such as the largest value that is reported, for updating a CI.").
* Control CI updates at the discovery source and CI attribute level.
* Visualize discovery sources of attribute values, at the attribute level.
* Modify reconciliation rules and then recompute CMDB data, reflecting the updated reconciliation rules.
* Revert CMDB data integration from a specific discovery source, if, for example, you realize that the discovery source is not reliable. Recompute CI attribute values, while excluding the discovery source that you want to ignore.
* Validate a new discovery source by comparing its data to data from other discovery sources, which are known to be valid.
* Improve data management, data quality, and operational insights, by querying on CMDB 360 data. Use the CMDB 360 query builder in CMDB Workspace or in Service Graph Workspace to create queries for CMDB 360 records, discovery sources, and CI records.
{#multisource-cmdb__ul_zdq_mlj_qlb}

## Enable and configure CMDB 360 {#multisource-cmdb__section_enable_multisource_CMDB}

* [Activate](https://www.servicenow.com/docs/access?context=t_ActivateAPlugin&version=brazil&pubname=brazil-platform-administration&ft:locale=en-US) the ITOM Discovery License (com.snc.itom.discovery.license) plugin.
* Navigate to AllConfigurationCMDB 360 Properties. Then, in the CMDB 360 Properties pane ensure that the [glide.identification_engine.multisource_enabled](https://www.servicenow.com/docs/vaIhXSKapk6dMjeknSXb9g "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.") (Enables CMDB 360) property is set to true.
* Optionally, [Exclude classes from CMDB 360](https://www.servicenow.com/docs/OpYiOMGe26JXQ~pFcMWw0Q "Prevent CMDB 360 from collecting, storing, and analyzing data for classes for which it isn't needed. CMDB 360 processes large amounts of data. Therefore, excluding classes can help improve the performance of the Multisource Dashboard Analytics Population scheduled job and of CMDB 360 queries.").
{#multisource-cmdb__ul_rx5_sjp_rlb}  
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](https://www.servicenow.com/docs/vaIhXSKapk6dMjeknSXb9g "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.") (Enables capturing CMDB 360 data for CIs from CMDB classes)
* [glide.identification_engine.multisource_non_cmdb_ci_enabled](https://www.servicenow.com/docs/vaIhXSKapk6dMjeknSXb9g "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.") (Enables capturing CMDB 360 data for CIs from non-CMDB classes)
{#multisource-cmdb__ul_rq2_d1s_qlb}

## Report on CMDB 360 data {#multisource-cmdb__section_yhh_v4r_qlb}

Use the or [CMDB 360 insights dashboard in CMDB Workspace](https://www.servicenow.com/docs/h87uoAgsgd6ImEPk0UCk~Q "The CMDB 360 insights dashboard provides aggregations and analysis of CMDB 360 data, where you can track activities and identify potential issues of discovery sources.") to gain insights into the CMDB 360 data store. Build reports that, for example, do the followings:  
* Find CIs not reported by any discovery source.
* Find discovery sources populating data in your CMDB.
* Compare attribute values across discovery sources.
* Compare attribute values between CMDB and other discovery source.
* Limit reports for CMDB 360 data, to a specific application service, technical service, or a CMDB group.
{#multisource-cmdb__ul_hpx_p1s_qlb}

## Visualize CMDB 360 data {#multisource-cmdb__section_rym_yhs_qlb}

CMDB 360 is highly verbose in the user interface:

* On the [Reconcliation Rules](https://www.servicenow.com/docs/0pT4QlDmKokSjVO3j6FBJw#create-reconciliation-rule "Create a static or a dynamic CI reconciliation rule.") page in CI Class Manager, click the Preview Data tab to see per attribute, discovery sources that are authorized to update that attribute, in precedence order.
* On a CI form, click the CMDB 360 Data Preview related link to see per CI attribute, current value in the CMDB and incoming values from other discovery sources.
{#multisource-cmdb__ul_hcm_nkl_hmb}

## Logging {#multisource-cmdb__section_qwr_lrg_rlb}

Enable logging for CMDB 360 by adding and enabling the system property ​ [glide.cmdb.logger.source.cmdb_multisource](https://www.servicenow.com/docs/vaIhXSKapk6dMjeknSXb9g "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties."). In the Log \[syslog\] table, search for
entries in which `source="cmdb_multisource"`.

*[\>]: and then