Target tables for storing API Service Graph Connector for Kong Konnect data

  • Release version: Yokohama
  • Updated February 5, 2026
  • 4 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 Target tables for storing API Service Graph Connector for Kong Konnect data

    The API Service Graph Connector for Kong Konnect integrates with your ServiceNow instance to facilitate the periodic retrieval of data from Kong Konnect applications. This data is stored in various tables, primarily extending from Configuration Item (CMDB) classes and some non-CMDB tables.

    Show full answer Show less

    Key Features

    • Kong Gateway [cmdbcikonggateway]: Attributes such as ID, Name, Asset tag, Correlation ID, Description, and Operational status are populated from the collected data.
    • Kong Data Plane Node [snkongkonnectkongdataplanenode]: Attributes including Hostname, Version, and Operational status are documented.
    • Cloud Service Account [cmdbcicloudserviceaccount]: Captures Account ID, Name, Datacenter Type, and Operational status.
    • Logical Datacenter [cmdbcilogicaldatacenter]: Stores Name, Object ID, Region, and Operational status.
    • Kong Load Balancer [cmdbcikonglb]: Collects attributes like ID, Name, Algorithm, and Operational status.
    • Kong Target [cmdbcikongtarget]: Records details such as ID, Description, Name, and Operational status.
    • Managed API [cmdbcimanagedapi]: Includes attributes like ID, Name, Base URL, and Operational status.
    • API Backend [cmdbciapibackend]: Captures Host, Path, URL, and Protocol details.
    • API Frontend [cmdbciapifrontend]: Includes attributes such as Host, Method, Path, and URL.
    • API Consumer [apiconsumer]: Records ID, Custom ID, Email, and Username.
    • API Consumer Subscription [apiconsumersubscription]: Captures Operational status, API Consumer ID, and Creation Date.
    • API Policy [apipolicy]: Includes Name, Managed API ID, Protocols, and Active status.

    Key Outcomes

    By implementing this connector, ServiceNow customers can efficiently manage and visualize the relationships between various API components, improving oversight and operational efficiency. This integration enables proactive monitoring and management of API services, ensuring that operational statuses and configurations are accurately reflected in the ServiceNow platform.

    When you complete setting up the connection, you can configure the integration to periodically pull data from a Kong Konnect application. The data is saved in tables that extend from the Configuration item [cmdb_ci] classes and other non-CMDB tables.

    Kong Gateway [cmdb_ci_kong_gateway]

    The following attributes in the Kong Gateway [cmdb_ci_kong_gateway] table are populated by collected data:
    Attribute label Attribute name
    ID id
    Name name
    Asset tag asset_tag
    Correlation ID correlation_id
    Description short_description
    Operational status operational_status
    Table 1. Relationships created for Kong Gateway
    Parent class Relationship type Child class
    Kong Gateway [cmdb_ci_kong_gateway] Provides::Provided by Kong Load Balancer [cmdb_ci_kong_lb]
    Kong Gateway [cmdb_ci_kong_gateway] Provides::Provided by Managed API [cmdb_ci_managed_api]
    Kong Gateway [cmdb_ci_kong_gateway] Uses::Used by DNS Alias [cmdb_ci_dns_alias]
    Kong Gateway [cmdb_ci_kong_gateway] Reference Key Value [cmdb_key_value]
    Kong Gateway [cmdb_ci_kong_gateway] Reference API Consumer [api_consumer]

    Kong Data Plane Node [sn_kong_konnect_kong_data_plane_node]

    The following attributes in the Kong Data Plane Node [sn_kong_konnect_kong_data_plane_node] table are populated by collected data:
    Attribute label Attribute name
    Hostname hostname
    Version version
    id ID
    Connection Alias SysId connectionaliassysid
    Operational status operational_status
    Table 2. Relationship created for Kong Data Plane Node
    Parent class Relationship type Child class
    Kong Data Plane Node [sn_kong_konnect_kong_data_plane_node] Reference Kong Gateway [cmdb_ci_kong_gateway]
    Note:
    This table is available within the API Service Graph Connector for Kong Konnect application (sn_kong_konnect) scope.

    Cloud Service Account [cmdb_ci_cloud_service_account]

    The following attributes in the Cloud Service Account [cmdb_ci_cloud_service_account] table are populated by collected data:
    Attribute label Attribute name
    Account Id account_id
    Name name
    Datacenter Type datacenter_type
    Operational status operational_status

    Logical Datacenter [cmdb_ci_logical_datacenter]

    The following attributes in the Logical Datacenter [cmdb_ci_logical_datacenter] table are populated by collected data:
    Attribute label Attribute name
    Name name
    Object ID object_id
    Region region
    Operational status operational_status
    Table 3. Relationships created for Logical Datacenter
    Parent class Relationship type Child class
    Logical Datacenter [cmdb_ci_logical_datacenter] Hosted on::Hosts Kong Gateway [cmdb_ci_kong_gateway]
    Logical Datacenter [cmdb_ci_logical_datacenter] Hosted on::Hosts Cloud Service Account [cmdb_ci_cloud_service_account]

    DNS Alias [cmdb_ci_dns_alias]

    The following attributes in the DNS Alias [cmdb_ci_dns_alias] table are populated by collected data:
    Attribute label Attribute name
    Name name
    Operational status operational_status

    Kong Load Balancer [cmdb_ci_kong_lb]

    The following attributes in the Kong Load Balancer [cmdb_ci_kong_lb] table are populated by collected data:
    Attribute label Attribute name
    ID id
    Name name
    Algorithm algorithm
    Description short_description
    Operational status operational_status
    Table 4. Relationship created for Kong Load Balancer
    Parent class Relationship type Child class
    Kong Load Balancer [cmdb_ci_kong_lb] Contains::Contained by Kong Target [cmdb_ci_kong_target]

    Kong Target [cmdb_ci_kong_target]

    The following attributes in the Kong Target [cmdb_ci_kong_target] table are populated by collected data:
    Attribute label Attribute name
    ID id
    Description short_description
    Name name
    Operational status operational_status
    Target target

    Managed API [cmdb_ci_managed_api]

    The following attributes in the Managed API [cmdb_ci_managed_api] table are populated by collected data:
    Attribute label Attribute name
    ID id
    Name name
    Base URL base_url
    Description short_description
    Operational status operational_status
    Life Cycle Stage Status life_cycle_stage_status
    Life Cycle Stage life_cycle_stage
    Type type
    Table 5. Relationships created for Managed API
    Parent class Relationship type Child class
    Managed API [cmdb_ci_managed_api] Uses::Used by API Frontend [cmdb_ci_api_frontend]
    Managed API [cmdb_ci_managed_api] Uses::Used by API Backend [cmdb_ci_api_backend]

    API Backend [cmdb_ci_api_backend]

    The following attributes in the API Backend [cmdb_ci_api_backend] table are populated by collected data:
    Attribute label Attribute name
    Host host
    ID id
    Path path
    URL url
    Name name
    Port port
    Protocol protocol
    Table 6. Relationship created for API Backend
    Parent class Relationship type Child class
    API Backend [cmdb_ci_api_backend] Uses::Used by Kong Load Balancer [cmdb_ci_kong_lb]

    API Frontend [cmdb_ci_api_frontend]

    The following attributes in the API Frontend [cmdb_ci_api_frontend] table are populated by collected data:
    Attribute label Attribute name
    Host host
    ID id
    Method method
    Path path
    URL url
    Description short_description
    Name name
    Operational status operational_status
    Protocol protocol
    Table 7. Relationship created for API Frontend
    Parent class Relationship type Child class
    API Frontend [cmdb_ci_api_frontend] Use End Point To::Use End Point From API Backend [cmdb_ci_api_backend]

    API Consumer [api_consumer]

    The following attributes in the API Consumer [api_consumer] table are populated by collected data:
    Attribute label Attribute name
    ID id
    Custom ID custom_id
    Email
    Note:
    Fetched using the Developers data source only.
    		 email
    Username username
    API Gateway api_gateway
    Table 8. Relationship created for API Consumer
    Parent class Relationship type Child class
    API Consumer [api_consumer] Reference Kong Gateway [cmdb_ci_kong_gateway]

    API Consumer Subscription [cmdb_ci_api_consumer_subscription]

    The following attributes in the API Consumer Subscription [cmdb_ci_api_consumer_subscription] table are populated by collected data:
    Attribute label Attribute name
    Operational status operational_status
    API Consumer api_consumer
    ID id
    Creation Date creation_date
    Description short_description
    Last Modified Date last_modified_date
    Name name
    Table 9. Relationship created for API Consumer Subscription
    Parent class Relationship type Child class
    API Gateway [cmdb_ci_api_gateway] Provides::Provided by API Consumer Subscription [cmdb_ci_api_consumer_subscription]

    API Consumer Access [api_consumer_access]

    The following attributes in the API Consumer Access [api_consumer_access] table are populated by collected data:
    Attribute label Attribute name
    API api
    API Consumer api_consumer
    State state
    API Consumer Subscription api_consumer_subscription

    API Policy [api_policy]

    The following attributes in the API Policy [api_policy] table are populated by collected data:
    Attribute label Attribute name
    Name name
    Managed API managed_api
    ID id
    Protocols protocols
    Frontend frontend
    Active active
    Consumer consumer
    Table 10. Relationship created for API Policy
    Parent class Relationship type Child class
    API Policy [api_policy] Reference Managed API [cmdb_ci_managed_api]

    Key Value [cmdb_key_value]

    The following attributes in the Key Value [cmdb_key_value] table are populated by collected data:
    Attribute label Attribute name
    Tag tag
    Configuration item configuration_item
    Key key
    Value value