API Service Graph Connector for Kong Konnect
Use the ServiceNow® API Service Graph Connector for Kong Konnect to import API details from a Kong Konnect service into the Configuration Management Database (CMDB).
Request apps on the Store
Visit the ServiceNow Store to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the ServiceNow Store version history release notes.
Key features
Import data into a normalized data model for consistency across other technologies.
The API Insights workspace provides a centralized interface where you can analyze and interact with API data, without needing direct access to Kong Konnect, enhancing visibility, governance, and collaboration across the API estate. To learn more, see API Insights.
Supported ServiceNow versions
- Xanadu
- Yokohama
- Zurich
Use cases
You can use the API Service Graph Connector for Kong Konnect to:
- Maintain an end-to-end inventory of defined APIs, identifying what APIs are published, used, and by whom.
- Track APIs from customer-facing endpoints to the underlying services, identifying impacted endpoints when services change or fail and creating incidents for reported issues.
- Address vulnerabilities and security incidents related to API endpoints and create compliance requirements to measure against.
Configuring a connection for the connector
You can configure a connection for the connector by using the SGC Central view in the CMDB Workspace. The view enables you to discover and install connectors, and then effectively manage the full life cycle of creating, editing, monitoring, and debugging connections. To configure the connector using SGC Central, see Configure API Service Graph Connector for Kong Konnect using SGC Central.
Data mapping
Data from the Kong Konnect data sources is mapped and transformed into the CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the CMDB using the Identification and Reconciliation Engine (IRE).
When you complete setting up the connection, you can configure the integration to periodically pull data from a Kong Konnect service.
The following table lists the data sources in the order they run, the staging tables, and the target tables as CMDB CI classes and non-CMDB tables for a Kong Konnect service.
| Data source | Staging table | Target tables |
|---|---|---|
| Gateway | Gateway \[sn\_kong\_konnect\_gateway\] | Kong GatewayDNS Alias Logical Datacenter Cloud Service Account Key Value |
| Data Plane Node | Data Plane Node \[sn\_kong\_konnect\_data\_plane\_node\] | Kong Data Plane Node |
| Load Balancer | Load Balancer \[sn\_kong\_konnect\_load\_balancer\] | Kong Load Balancer |
| Target | Target \[sn\_kong\_konnect\_target\] | Kong Target |
| Services | Services \[sn\_kong\_konnect\_services\] | Managed APIAPI Backend Key Value |
| Routes | Routes \[sn\_kong\_konnect\_routes\] | API Frontend |
| Consumer | Consumer \[sn\_kong\_konnect\_consumer\] | API Consumer |
| Policy | Policy \[sn\_kong\_konnect\_policy\] | API Policy |
| Developers | Developers \[sn\_kong\_konnect\_developers\] | API Consumer |
| Applications | Applications \[sn\_kong\_konnect\_applications\] | API Consumer Subscription |
| API Consumer Access | API Consumer Access \[sn\_kong\_konnect\_api\_consumer\_access\] | API Consumer Access |
For more information on where data is saved when pulling data from a Kong Konnect service, see Target tables for storing API Service Graph Connector for Kong Konnect data.
You can use the IntegrationHub ETL app to view the data maps. See IntegrationHub ETL for more information.
Record removal process
The connector supports soft deletion for CMDB CI classes only, meaning records are not permanently removed from the system. Instead, any CMDB CI records not discovered during the last scheduled job run are marked as Non-Operational.