Data integration checklist for Data Foundations in CMDB success advisor

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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 Data Integration Checklist for Data Foundations in CMDB Success Advisor

    The data integration checklist is designed to ensure that Discovery patterns and Service Graph Connectors are properly configured and actively contributing to your Configuration Management Database (CMDB). This checklist is essential for maintaining high-quality foundational data within your CMDB.

    Show full answer Show less

    Key Features

    Discovery Patterns Checklist

    • Pattern Name: Verify the relevance of the discovery pattern for your principal classes.
    • Status: Ensure the pattern is active; only active patterns contribute data.
    • Attribute Coverage: Assess the number of CI attributes populated; low coverage may indicate issues.
    • Suggested Version: Plan to upgrade to the latest suggested version for optimal coverage.
    • Installed Version: Compare with the suggested version and upgrade as necessary.
    • View Pattern: Access the link to review or modify the pattern configuration.

    Service Graph Connectors Checklist

    • Connector Name: Confirm that the connector is necessary for your principal classes.
    • Status: Activate any needed but currently inactive connectors.
    • Attribute Coverage: Check the number of hardware attributes populated; low coverage may indicate mapping issues.
    • Suggested Version: Upgrade to the latest suggested version for better coverage.
    • Installed Version: Ensure the version in use meets suggested standards.
    • Active Connections: Confirm at least one active connection per principal class.
    • Inactive Connections: Review and troubleshoot any connections that are not active.

    Key Outcomes

    Upon completing the checklist, ensure that:

    • All relevant Discovery patterns are active.
    • At least one Service Graph Connector is active for each principal CI class.
    • Attribute coverage supports your Data Foundations goals.
    • Integrations are accurately populating essential ownership and relationship attributes.
    • CMDB records for principal classes are complete and accurate.

    Use the data integration checklist to verify that Discovery patterns and Service Graph Connectors are correctly configured and actively contributing to your Configuration Management Database (CMDB), promoting quality foundational data.

    Discovery patterns checklist

    Confirm each Discovery pattern is enabled and effectively populating attributes for your principal classes.

    Table 1. Discovery patterns configuration checks
    Select Check item (field) Description Action
    Pattern name Name of the discovery pattern contributing CI data for Data Foundations. Confirm that the pattern is relevant for your principal classes.
    Status Current state of the pattern as active or inactive. Only active patterns contribute data. Verify that the pattern is active with Status set to Active to confirm it’s contributing data.
    Attribute coverage Number of CI attributes populated by the pattern. Check how many relevant CI attributes are populated for each principal class.
    Note:
    Low attribute coverage may suggest shallow discovery or misaligned pattern logic.
    Suggested version Latest suggested version for optimal attribute coverage. Plan and perform an upgrade to the suggested version or higher to improve coverage.
    Installed version Version currently in use in your instance. Compare with the suggested version and upgrade if necessary.
    View pattern Link to inspect the pattern configuration. Select the link to review or modify the pattern logic.

    Service Graph Connectors checklist

    Confirm Service Graph Connectors are installed and actively contributing hardware data.

    Table 2. Service Graph Connectors configuration checks
    Select Check item (field) Description Action
    Connector name Name of the Service Graph Connector providing CI data for Data Foundations. Confirm that the Service Graph Connector is required for your principal classes.
    Status Current state of the Service Graph Connector as active or inactive. Activate Service Graph Connectors that are needed for Data Foundations but currently inactive.
    Attribute coverage Number of hardware attributes populated by the Service Graph Connector. Check how many relevant CI attributes are being populated for each principal class.
    Note:
    Low coverage may indicate incomplete mappings or missing source data.
    Suggested version Latest suggested version for optimal attribute coverage. Plan and perform an upgrade to the suggested version or higher to improve coverage.
    Installed version Version currently in use in your instance. Compare with the suggested version and upgrade if necessary.
    Active connections Number of active connections. Confirm that at least one connection is actively importing data per principal class.
    Inactive connections Number of inactive connections. Review and troubleshoot any configured connections that aren’t currently active.

    Optional checks for Discovery patterns and Service Graph Connectors

    Table 3. Optional data integration checks
    Select Check item Description Action
    No entitlements warning Discovery patterns or Service Graph Connectors tile showing no entitlements, indicating missing access or licensing. Verify licensing and entitlements with your administrator.
    Suggested integrations reviewed Some Discovery patterns are listed as suggestions because they aren’t installed or active, and some Discovery patterns are listed but are not actively used. Evaluate business need and consider implementing high-value suggested integrations.

    Final validation

    Once all data integration checks are complete:

    • Discovery patterns relevant to your principal classes are active.
    • At least one Service Graph Connector is active for each principal CI class in your DF scope.
    • Attribute coverage across integrations supports your Data Foundations outcome.
    • Integrations are populating ownership, relationship, and key infrastructure attributes.
    • CMDB records for principal classes are accurate and complete.