---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Insights view in CMDB Workspace

# Insights view in CMDB Workspace {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 18 Minuten Lesedauer

Use the Insights view in CMDB Workspace to see and increase the level of adoption of key CMDB features and application services to improve the overall health of the CMDB. Explore how tools and features can maximize the health and efficiency of
your CMDB and use direct links to install and start using features immediately.

## Access {#cmdb-workspace-insights-view__section_ifz_njk_wwb}

Role requirement: sn_cmdb_user (CMDB User), or a user role containing sn_cmdb_user (sn_cmdb_admin, sn_cmdb_editor).

To access the Insights view, navigate to WorkspacesCMDB Workspace and then select Insights in the CMDB Workspace menu bar.
The Insights view includes the following tiles:

* CMDB feature adoption
* CMDB performance insights
* Application services
* Cloud vs Non-cloud resources
{#cmdb-workspace-insights-view__ul_hxy_t3v_1xb}

## CMDB feature adoption {#cmdb-workspace-insights-view__section_a35_l2l_wwb}

Shows dial charts for the overall adoption levels of all three categories of CMDB tools and features:

Data ingestion
:   Tools and features that support and ensure ingestion of high-quality data into the CMDB.

Data governance
:   Tools and features that let you manage the CMDB data after it has been ingested.

Search and analytics
:   Tools and features that provide meaningful and helpful insights into the CMDB data.

Select each dial chart in the tile to access its tab and associated cards with further details about the features in the category. Pay special attention to categories with low levels of adoption and those features that aren't yet
implemented in the instance and which you should consider for adoption.  
Each category tab shows cards for the features in the category and the following general cards:

* Overall adoption level for the tab: The calculated overall level of adoption for the tab. Calculations are specific for each tab, and can be based, for example, on the level of adoption of some or all the features in the tab.
* Adoption progress: Installation, activation, or usage status per feature in the tab. Select a feature link to access a relevant resource such as the feature's landing page with an overview dashboard or an installation location.
{#cmdb-workspace-insights-view__ul_ly3_pzs_wwb}  
Depending on adoption level, a card might contain any of the following resource links:

* Learn more: Link to documentation to learn and explore the benefits and usage of the feature.
* View demo: Link to a short demo about the feature.
* Get started: Link to a landing page where you can start immediately utilizing the feature.
* Install app: Link to the ServiceNow Store where you can immediately install the app.
{#cmdb-workspace-insights-view__ul_ffx_flk_wwb}  
Cards use different methods to examine the instance and determine if the card's feature is installed, activated, and being used. For example, some cards check for the installation status of plugins and some cards rely on data in the specific feature tables. Many counts and aggregation data that appear on cards is based on [Performance Analytics indicators](https://www.servicenow.com/docs/access?context=c_Indicators&version=australia&pubname=australia-now-intelligence&ft:locale=en-US) built on top of the Base Aggregate Data \[sn_cmdb_ws_base_aggregate_data\] table.

* If the result is that the card's feature is installed or being used, then the card shows charts and counts about the level of usage. In which case, the card's label might slightly adjust.
* If the result is that the card's feature isn't installed or isn't in use, then links are provided to resources where you can explore, install, and start using the feature.
{#cmdb-workspace-insights-view__ul_fjd_hj3_fxb}

Most of the cards scheduled jobs run every 24 hours, therefore, depending on the type of data, some card data is based on recent but not current data. The Last updated timestamp in the cards reflects the collection time for the
data that was used for the card. Also, immediately after getting started with a feature, a card won't reflect on the latest status or usage of the feature, until up to 24 hours when the card's scheduled job runs (for the CIs
processed by IRE based on source card, the associated scheduled job, CMDB Workspace - Populate aggregates Monthly, runs monthly).

The following sections provide details for each card, including the calculation script used for the card.

## CMDB feature adoption: Data ingestion {#cmdb-workspace-insights-view__section_r3g_dkk_wwb}

The overall adoption level for data ingestion maps to the following findings in the instance:

* Low (red): Less than 80% of CIs are processed by Identification and Reconciliation Engine (IRE)
* Moderate (amber): 80---90% of CIs are processed by IRE
* High (green): Over 90% of CIs are processed by IRE
{#cmdb-workspace-insights-view__ul_pkq_bxz_wwb}  
Data ingestion contains the following features and aggregations:

CIs processed by IRE

:   Determines the percentage of CIs that are processed by [IRE](https://servicenow-prod.fluidtopics.net/Z0vdyA7BYiBt_YX8qkVWyQ "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."), by checking the Source \[sys_object_source\] table. CIs that aren't processed by IRE introduce a data integrity risk.

    The percentage of CIs that are being processed by IRE determines both, the level of adoption for this feature card and the overall adoption level for the entire data ingestion category.

Service Graph Connectors
:   Determines the installation and usage status of [Getting started with Service Graph Connectors](https://servicenow-prod.fluidtopics.net/1wLEV8ubYlPM_nDUSO~F~Q "Service Graph Connectors, including API Service Graph Connectors, are predefined integrations that ingest third-party data and API data into the Configuration Management Database (CMDB) from various domains, such as security, servers, software or monitoring, Internet of Things (IoT), and cloud."), by checking:

    * If the ITOM Licensing plugin (com.snc.itom.license) is active
    * If there is at least one Service Graph Connector installed in the instance
    {#cmdb-workspace-insights-view__ul_ngy_pnz_wwb}

    If Service Graph Connectors are installed and are in use, then the card shows a count of those connectors.

    Hinweis:  
    The count of Service Graph connectors that appears on the card might be slightly different than the number of connectors that show on the ServiceNow Store site because the counting methods that are used are different.

IntegrationHub ETL

:   Determines whether the [IntegrationHub ETL](https://servicenow-prod.fluidtopics.net/o3eK_l0nhtAcQ_AgXuZ95Q "Use the IntegrationHub ETL store app to create and manage ETL transform maps, which integrate third-party data into the CMDB or into non-CMDB tables without compromising the integrity of data. IntegrationHub ETL provides a simplified user interface that guides you through the integration process end-to-end, including a test integration run of sample data.") store app is installed and used, based on records in the CMDB Integration Studio Application Data Sources \[cmdb_inst_application_feed\] table. If IntegrationHub ETL is
    in use, then the card shows a count of ETL transform maps in IntegrationHub ETL (demo ETL transform maps aren't counted).

    Select View ETL transform maps to open IntegrationHub ETL where you can examine existing ETL transform maps and create new ones.

CIs processed by IRE based on source

:   Chart showing CIs processed by IRE, grouped by Service Graph Connectors, ServiceNow Discovery, a combination of both, and others, for the past six months.

    The following discovery sources are counted as ServiceNow Discovery:

    * ServiceNow
    * ServiceWatch
    * ACC-Visibility
    * AgentClientCollector
    * CredentiallessDiscovery
    {#cmdb-workspace-insights-view__ul_shh_d5c_dxb}

    Point to the chart to show monthly aggregation data.

    This card is hidden if there are no CIs processed by IRE.

CMDB application for APIs and CLI

:   Determines whether the [CMDB application for APIs and CLI](https://www.servicenow.com/docs/access?context=cmdb-cli-commands&version=australia&pubname=australia-application-development&ft:locale=en-US) store app is installed.

    This card appears only if the store app isn't installed, providing helpful resources for exploration and adoption.

## CMDB feature adoption: Data governance {#cmdb-workspace-insights-view__section_w2m_rkk_wwb}

The overall adoption level for data governance maps to the following findings in the instance:

* Low (red): Less than 33% of features are used
* Moderate (amber): 33---66% of features are used
* High (green): Over 66% of features are used
{#cmdb-workspace-insights-view__ul_i3y_dxz_wwb}  
The overall level of adoption of data governance is based on whether [CMDB Data Manager](https://servicenow-prod.fluidtopics.net/zeNbPK7ZTjzGDZbz47i18w "The integrity and health of the CMDB is essential for the various features that depend on the data in the CMDB. As the CMDB grows and infrastructures change, the CMDB can accumulate stale, duplicate, or outdated CIs and therefore no longer accurately reflect the IT infrastructure and applications in the organization.") features are used.  
Hinweis:  
Historical data might not be available for all past 90 days because CMDB Workspace version 3.4, which relies on Performance Analytics indicators to collect and save historical usage data, was deployed less than 90 days ago. This situation might result in a discrepancy between actual usage and what the card shows.

CMDB Data Manager/CIs used in Data Manager policies
:   Determines usage by checking if either of the following conditions is true:

    * There are any user-created Delete, Retire, or Archive policies (by searching table CMDB Data Manager Policy and Attributes \[cmdb_data_manager_policy_and_attributes\])
    * There are any CIs processed by these user-created Delete, Retire, or Archive policies, in the last 90 days (by searching table CMDB Data Management Policy Executions \[cmdb_data_management_policy_execution\])
    {#cmdb-workspace-insights-view__ul_iyy_f4p_fxb} If CMDB Data Manager is in use, shows a chart with CIs that were processed by these policies in the past six months, by month, and by policy type.

Data attestation/CIs used in data attestation

:   Determines usage by checking if either of the following conditions is true:

    * There are any user-created [Attestation policies](https://servicenow-prod.fluidtopics.net/qnMFVewZj5nZyZeJJtj54A "Verify the existence of actual IT infrastructure and applications that you own, systematically and in bulk. As CIs are continuously ingested into the CMDB from various data sources, ensure the integrity of the CMDB. Remove any stale CIs that are associated with IT infrastructure or applications that no longer exists.") (by searching table CMDB Data Manager Policy and Attributes \[cmdb_data_manager_policy_and_attributes\])
    * There are any CIs processed by these user-created Attestation policies, in the last 90 days (by searching table CMDB Data Management Policy Executions \[cmdb_data_management_policy_execution\])

    {#cmdb-workspace-insights-view__ul_jf2_spp_fxb}

    If data attestation is in use, shows a chart with CIs that were processed by attestation policy tasks in the past six months, by month.

Data synchronization

:   Checks if there is at least one class for which the managed_by_group attribute is globally set so that all class CIs are synchronized on the same value.

    For information about synchronizing group assignment attributes using the CI Class Manager, see [Set the group for a CI or an entire class of CIs](https://servicenow-prod.fluidtopics.net/ZFcC3WeyJQUuHIdWWULdgA "Synchronize group assignment attributes on entire CI classes and individual CIs using the CI Class Manager.") and [Synchronizing group assignment attributes](https://servicenow-prod.fluidtopics.net/jAoDav7dQALQmKoPMdLrjA "To empower a particular user group to manage a collection of CIs or CI classes, set group assignment attributes through the Technology management offering or the CI Class Manager. The operation synchronizes the group attribute data across all CIs that belong to the specified CI class or groups of CIs.").

    The Data synchronization card is available starting with CMDB Workspace v3.6.

Principal classes

:   Checks if the Principal Class filter is configured with at least one principal class. The Principal Class filter limits the number of CIs that appear in list views, to show only CIs of principal classes. Reducing the amount
    of data in list views to only relevant data, improves performance and efficiency.

    For more information about managing the Principal Class filter in CI Class Manager, see [Update the list of classes in the Principal Class filter](https://servicenow-prod.fluidtopics.net/ToBHZIiQb6wDdaUmCOVWMQ "A Principal Class is a designation for those CMDB classes that are most critical for foundational data health and governance in the organization. Manage the list of classes in the Principal Class filter so that those classes are prioritized for tracking, health, certification, lifecycle management, and class list views.").

    The Principal class card is available starting with CMDB Workspace v3.6.

## CMDB feature adoption: Search \& analytics {#cmdb-workspace-insights-view__section_krk_skk_wwb}

The overall adoption level for search \& analytics maps to the following findings in the instance:

* Low (red): Less than 33% of features are used
* Moderate (amber): 33---66% of features are used
* High (green): Over 66% of features are used
{#cmdb-workspace-insights-view__ul_grw_2xz_wwb}  
Search \& analytics contains the following features and aggregations:

CMDB Query Builder/Query Builder queries
:   Determines if the [CMDB Query Builder](https://servicenow-prod.fluidtopics.net/dzypqKPNpKS3I3hMqRu8Ww "The CMDB Query Builder enables you to build complex infrastructure and service queries that span multiple CMDB classes, non-CMDB tables, and that involve many CIs that are connected by different relationships.") is in use, by checking if either of the following conditions is true:

    * There are any records in the Saved Queries \[qb_saved_query\] table in which Source is QB
    * There are any queries executed or queries executed with reports, in the last 90 days  
      Hinweis:  
      Historical data might not be available for all past 90 days because CMDB Workspace version 3.4, which relies on Performance Analytics indicators to collect and save historical usage data, was deployed less than 90 days ago. This situation might result in a discrepancy between actual usage and what the card shows.
    {#cmdb-workspace-insights-view__ul_stw_jtd_dxb}If CMDB Query Builder is in use, shows a chart with counts of query executions and query executions in reports, for the past six months, by month.

    Point to the chart to see monthly aggregation data.

Intelligent search
:   Determines if [Intelligent Search for CMDB](https://servicenow-prod.fluidtopics.net/4~y_0jxqxSWzkJZpzoMetA "Use everyday natural language query (NLQ) in a search string to query for a set of CIs in the CMDB. Intelligent Search for CMDB, parses, resolves ambiguities, and converts your search string into a valid CMDB query. Complex search strings open fully constructed on a canvas of CMDB Query Builder where you can continue and refine, or run.") is in use by checking the NLQ Query Logs \[nlq_query_log\] table for any records where source is CMDB_WS, from the past 90 days. If Intelligent Search is in use, shows counts of Intelligent Search queries for the past six months, by month.  
    Hinweis:  
    Historical data might not be available for all past 90 days because CMDB Workspace version 3.4, which relies on Performance Analytics indicators to collect and save historical usage data, was deployed less than 90 days ago. This situation might result in a discrepancy between actual usage and what the card shows.

CMDB 360 --- Records in Multisource

:   Total number of raw [CMDB 360](https://servicenow-prod.fluidtopics.net/XR19OO83T13l43jwc4D85w "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.") records in the CMDB 360 data store that contains records for each discovery source report, per each CI attribute. This card is identical to the [Total CMDB 360 records](https://servicenow-prod.fluidtopics.net/e~AK3tKMymU65vt8pSKiEQ "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.") card in the Discovery Sources tile in the CMDB 360 view.

    This card appears only if CMDB 360 is enabled, which is determined by checking the ITOM Discovery License (com.snc.itom.discovery.license) plugin and the system property [glide.identification_engine.multisource_enabled](https://servicenow-prod.fluidtopics.net/bsIeCXJv~yYKCI9clAlSVQ "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.").

CMDB 360 queries

:   Count of CMDB 360 queries that exist in the CMDB Multisource Queries \[cmdb_multisource_query\] table.

    This card appears only if CMDB 360 is enabled, which is determined by checking the ITOM Discovery License (com.snc.itom.discovery.license) plugin and the system property [glide.identification_engine.multisource_enabled](https://servicenow-prod.fluidtopics.net/bsIeCXJv~yYKCI9clAlSVQ "Several types of components are related to CMDB 360 (included in the com.snc.cmdb plugin), such as tables and properties.").

CMDB Data Foundation dashboard

:   Determines if the [CMDB and CSDM Data Foundations Dashboards](https://servicenow-prod.fluidtopics.net/zkHqKHPMBnY49ns_8M8IlA "The ServiceNow CSDM and CMDB Data Foundations Dashboards store app contains dashboards with insights into the key foundational metrics of your CMDB and Common Service Data Model (CSDM). This app uses ServiceNow health benchmarks to provide recommendations to ensure that the CMDB and CSDM are properly configured for optimal usage and to mitigate any potential risks.") store app (which includes the CMDB Data Foundation dashboard) is installed.

    This card appears only if the store app isn't installed, providing helpful resources for exploration and adoption. However, the feature is still included in calculating the search \& analytics overall level of
    adoption.

CMDB Health Dashboard

:   Determines if [CMDB Health](https://servicenow-prod.fluidtopics.net/NyBaS6P15nmPL~s6u2YgGg "A healthy CMDB, based on health benchmarks in an organization, is essential to an effective and continuous use of the product. Health indicators such as duplicate CIs, required CI fields, and audits are evaluated and aggregated into health scores at the class, health group, and service levels. CMDB Health also provides a framework for applying standardized CI remediation.") is in use by checking if at least one CMDB Health Dashboard job is enabled.

    This card appears only if the feature isn't in use, providing helpful resources for exploration and adoption. However, the feature is still included in calculating the search \& analytics overall level of adoption.

## CMDB performance insights {#cmdb-workspace-insights-view__section_fdf_hjb_fyb}

CMDB performance insights is available starting with CMDB Workspace v3.6 and only appears for users with the sn_cmdb_admin (CMDB Admin) role.

CMDB performance insights helps you understand the ways in which your configurations impact the performance of your CMDB. You can use the charts and tools within CMDB performance insights to troubleshoot, debug, or diagnose
performance issues. CMDB performance insights also analyzes your CMDB and Service Graph Connectors on your instance to generate recommendations on how you can improve the performance of your CMDB. The CMDB performance insights tile itself can show up to two of those recommendations.

Select View performance insights to access the CMDB performance insights data.  
The Payloads \& CIs tab contains the following tiles:

Partial payloads
:   Partial payloads occur when the data source didn't provide enough information to uniquely identify the CI, preventing IRE from processing the CI.

    * Total partial payload count:Shows the total number of partial payloads that exist in your instance. Large numbers of partial payloads in your instance can cause performance deterioration of the CMDB.

      For more
      information about partial payloads, see [Identification and Reconciliation Engine (IRE)](https://servicenow-prod.fluidtopics.net/sjBf8XCF9ptVTurEi7FuQg "IRE is an underlying key component in Identification and Reconciliation, providing a centralized framework to perform identification and reconciliation processes across different data sources. IRE uses identification rules, reconciliation rules, and IRE data source rules when processing incoming data before inserting that data to the CMDB.").
    * Discovery source:Breaks down the number of partial payloads by discovery sources. You can drill down on slices in this pie chart to see the list of partial payloads with errors, filtered by discovery source.

      You
      can drill down on specific partial payloads to better understand the error that you're experiencing. When you drill down on a partial payload, you can see the full payload item, which you can review to troubleshoot and
      address the specific errors.

      For more information about error types, see [Using identification simulation](https://servicenow-prod.fluidtopics.net/sD36MHY810WTKICzlQYBuA#identification-simulation "Identification simulation is a central location for automatically constructing a payload that is guaranteed to be complete and valid. You can then simulate the processing of the payload by the Identification and Reconciliation Engine (IRE) and examine the results before actually submitting it for execution by IRE.").
    {#cmdb-workspace-insights-view__ul_dhf_3kb_fyb}

Related records
:   Data about related records that are missing references. A record is missing a reference when the Referenced field for that record is empty.

    * Related records missing reference:Shows the total number of records that do not reference a CI in the Referenced field in the Related table. You can see a full list of the Related tables and the
      associated Referenced fields in the Related Entries \[cmdb_related_entry\] table.

      For more information about Related tables, see [Overview of CMDB](https://servicenow-prod.fluidtopics.net/OEiFKjMCThQweHfG4Yt0ww "The Configuration Management Database (CMDB) creates and maintains the logical configurations your network infrastructure needs to support a ServiceNow service.").
    * Related records missing reference by table:Breaks down the number of CMDB records missing references, by table. You can drill down on slices in this chart to see the list of specific records filtered by
      table.

      Before you can drill down on a slice of this pie chart, you must have any user roles required to view the table.

      You can also select New from the list view to create a new
      related entry table record. For more information about creating or editing a related entry table record, see [Edit a related table from CMDB performance insights](https://servicenow-prod.fluidtopics.net/qyt9jMZ0ZlzqYe~1s9l5kA "Edit a related table on the Related Entries [cmdb_related_entry] table directly from the CMDB performance insights tool in the CMDB Workspace Insights view. Update the related table to correctly reference another CI in the Referenced field when a reference is missing from the related table.").
    {#cmdb-workspace-insights-view__ul_kw5_jkb_fyb}

Duplicate and stale CIs
:   A CI is flagged as duplicate during identification and reconciliation. A CI is flagged as stale if it has not been updated within the Effective Duration time period specified in the [CMDB Health staleness rule](https://servicenow-prod.fluidtopics.net/c4e4IgZBIaOKCIvupGoBwA "If the staleness metric is in effect, then staleness rules are used to determine the percentage of stale CIs in the CMDB. This sum is then aggregated into the correctness KPI.") for the CI class.

    * CIs:Shows the number of CIs that are either duplicate or stale.

    * Stale records by class:Breaks down the number of stale CIs based on the CI class. You can drill down on slices in this pie chart to see the list of specific CI records filtered by class.

      For more information
      about stale CIs, see [CMDB Health KPIs and metrics](https://servicenow-prod.fluidtopics.net/RNQsx30XrnMFj5vsfp96Rw "CMDB Health calculates an aggregated score for three Key Performance Indicators (KPIs) which are correctness, compliance, and completeness, each further consisting of sub-metrics.").
    * Duplicate records by class:Breaks down the number of duplicate CIs based on the CI class. You can drill down on slices in this pie chart to see the list of specific CI records.

      For more information about
      duplicate CIs, see [Duplicate CIs remediation](https://servicenow-prod.fluidtopics.net/nlGsVsAC4XQomS3Xpqmtkg "Duplicate CIs in the CMDB unnecessarily overload the system and interfere with the CMDB's integrity and reliability. It is therefore important to regularly use CMDB tools that detect and remediate duplicate CIs.").
    {#cmdb-workspace-insights-view__ul_dy1_lkb_fyb}

Relationship records missing parent or child
:   Shows the trend line and number of relationship records in the CI Relationships \[cmdb_rel_ci\] table that are missing a parent or child CI. CIs that are missing a parent or child are considered invalid records and can have a
    performance impact on your instance.

Recommendations

:   Recommendations on this panel include a link to the related documentation and typically enable direct access to the associated tool, feature, or system property. Expand or minimize the panel by selecting the light bulb
    icon.

    The first two recommendations appear on the CMDB performance insights tile of the Insights view.

    You can only see a recommendation if you have the roles needed to access the feature, tool, or system property. Users with the sn_cmdb_admin role can hide recommendations or adjust the order in which recommendations appear.
Users can use the Active and Order fields in the CMDB WS Imp Action Card Config \[sn_cmdb_ws_imp_action_card_config\] table to configure those elements.  
The Service Graph connectors tab contains the following tiles:  
Hinweis:  
* The Service Graph connectors tab only appears if your instance has at least one Service Graph Connector and you have the cmdb_inst_admin role.
* To edit data source or scheduled data import records from CMDB Workspace, you may need to set Application scope to the Application of the data source or data import.
{#cmdb-workspace-insights-view__ul_xxx_mpb_fyb}

Connectors data source
:   Configurations on your Service Graph Connector data sources affect the ingestion and processing of incoming data. Changing your Service Graph Connector data source configurations can streamline data handling, making your CMDB more efficient and reducing impacts on the performance of your instance.

    * Sources with batch processing turned off:Shows the percentage of Service Graph Connector data sources in the Data Sources \[sys_data_source\] table with disabled Use Batch Import. It also lists the total number of data sources, and the number of data sources
      with enabled or disabled batch processing.

      To enable batch processing, access the record of a specific data source from the list view and select Use Batch Import. For more information about
      batch processing, see [Data source fields](https://www.servicenow.com/docs/access?context=r_DataSourceFileTypeFields&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).

      You can also select Edit to update a data source from the list view. For more information about editing a data source, see [Edit a data source from CMDB performance insights](https://servicenow-prod.fluidtopics.net/GZks3u9zKn5jevgfymJ2Ow "Edit a data source for your Service Graph Connectors to specify the data that an import set should ingest. Consider configuring a batch process to make ingestion more efficient and improve performance.").
    * Sources with concurrent import turned off:Shows the percentage of scheduled data imports of Service Graph Connector data sources in the Scheduled Data Imports \[scheduled_import_set\] table with Concurrent Import turned off. It also lists the total number of scheduled data imports,
      and the number of scheduled data imports with Concurrent Import turned on or off.

      To enable concurrent import, access the record of a specific scheduled data import from the list view and
      select Concurrent Import. For more information about concurrent import, see [Concurrent imports](https://www.servicenow.com/docs/access?context=concurrent-imports&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).

      You can also select Edit to update a scheduled data import from the list view. For more information about editing a scheduled data import, see [Edit a scheduled data import from CMDB performance insights](https://servicenow-prod.fluidtopics.net/OA5KDa9OrHICjRkgY4fmxg "Edit a scheduled data import directly from CMDB performance insights for your Service Graph Connectors. Consider enabling Concurrent Import with a custom size partition to split incoming data into multiple import sets and transform the import sets concurrently to reduce processing time.").
    * Sources with non-custom size partition method:Shows the percentage of scheduled data imports of Service Graph Connector data sources in the Scheduled Data Imports \[scheduled_import_set\] table that use a non-custom size partition method. It also lists the total number of scheduled data imports, and the number
      of scheduled data imports that use a non-custom size partition method.

      To use a custom size partition method, access the record of a specific scheduled data import from the list view. Ensure that
      Concurrent Import is selected. From the Partition Method drop-down menu that appears, select Custom size. For more information about partition
      methods, see [Schedule a data import](https://www.servicenow.com/docs/access?context=t_ScheduleADataImport&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).

      You can also select Edit to update a new scheduled data import from the list view. For more information about editing a scheduled data import,
      see [Edit a scheduled data import from CMDB performance insights](https://servicenow-prod.fluidtopics.net/OA5KDa9OrHICjRkgY4fmxg "Edit a scheduled data import directly from CMDB performance insights for your Service Graph Connectors. Consider enabling Concurrent Import with a custom size partition to split incoming data into multiple import sets and transform the import sets concurrently to reduce processing time.").
    {#cmdb-workspace-insights-view__ul_z3y_cqb_fyb}

Connectors execution trends
:   Aggregates Service Graph Connectors with outlier connector executions, where the number of imported rows or the rate of processing is significantly higher or lower than the 30-day trend.

    * Connectors with processing rate outliers:Shows the number of Service Graph Connectors that are considered outliers with connector execution processing rates outside the expected trend lines within the past 30 days.

    * Connectors with import count outliers:Shows the number of Service Graph Connectors that are considered outliers with connector execution import counts outside the expected trend lines within the past 30 days.

    {#cmdb-workspace-insights-view__ul_ddr_nqb_fyb}

    You can drill down the cards in the Connectors execution trends tile to access the Service Graph connector execution trends window. In that windows, a Service Graph Connector is available in the connectors drop-down menu only if it has an execution record.  
    Click the tabs on the Service Graph connector execution trends window to view the following charts and the Connector Execution list view of executed connector import sets:

    * Processing rate:Models the trend line of processing rates for connector executions. Shows the rate at which a connector processes rows of data over a period of time.

      There are two zones, which are the
      Confidence Band and the Prediction Band. Service Graph Connectors with connection executions that have processing rates outside of the Prediction Band are considered outliers. These zones don't appear when you select more than one Service Graph Connector.
    * Import count:Models the trend line of rows processed for connector executions. Shows the number of rows a connector processes over a period of time.

      There are two zones, which are the Confidence Band and the
      Prediction Band. Service Graph Connectors with connector executions that have import row counts outside of the Prediction Band are considered outliers.

    {#cmdb-workspace-insights-view__ul_wmm_4sb_fyb}On both charts, you can select outlier and non-outlier Service Graph Connectors to see the trend lines against each other.

For more information about processing data with Service Graph Connectors, see [Getting started with Service Graph Connectors](https://servicenow-prod.fluidtopics.net/1wLEV8ubYlPM_nDUSO~F~Q "Service Graph Connectors, including API Service Graph Connectors, are predefined integrations that ingest third-party data and API data into the Configuration Management Database (CMDB) from various domains, such as security, servers, software or monitoring, Internet of Things (IoT), and cloud.").

## Cloud vs Non-cloud resources {#cmdb-workspace-insights-view__section_ljr_dkk_wwb}

Charts showing counts and details for resources and application services that are hosted on various cloud services versus those that aren't. Resources and application services can be deployed on cloud services such as the Microsoft Azure Cloud, or on the local instance or other non-cloud solutions. For some ongoing operations in the organization,
it might be necessary to have those details which can be difficult to obtain.

For details about this chartthe charts, see 'Cloud vs Non-cloud resources' in the [Home view in CMDB Workspace](https://servicenow-prod.fluidtopics.net/mzYESOVzfLcBF5yfWfCU6A "Home view is the default view in CMDB Workspace. It shows important tasks that you should tend to, various counts for activities in CMDB such as new CIs, CMDB Health aggregations, and various charts. The Home view also provides several links with immediate access to key CMDB tools.") topic.

## Application services {#cmdb-workspace-insights-view__section_kql_dkk_wwb}

Shows a count of [application services](https://servicenow-prod.fluidtopics.net/b_V6yURBatarJl_aQB8qBA "Understand application services, learn about different application service types and how multiple ServiceNow business units and products use them.") in your organization, based on records in the Service Instance \[cmdb_ci_service_auto\] table. The chart shows the trend of total number of application services per day, for
the past seven days.

Select the tile to access the Application Services dashboard where you can monitor the adoption level and health of application services. For details about the Application Services dashboard, see [Use Service instance (Application Services) dashboard to monitor health](https://servicenow-prod.fluidtopics.net/1VSpKvrLXKA3GdVoCWNgSg "Use insights from the Service instance dashboard to reduce the number of incomplete Service instances by populating them and adding missing data. To use service instances effectively, ensure that service instances are fully configured and are populated.").

