Service Graph Connector for Observability - Dynatrace SaaS is designed for the Dynatrace SaaS (3rd‑generation) platform and leverages DQL-based APIs and the modern Grail architecture to import data from Dynatrace into the Configuration Management Database (CMDB).
The Service Graph Connector for Observability - Dynatrace SaaS imports the following data from Dynatrace to the ServiceNow CMDB:
- Hosts
- Processes
- Services
- Frontends
A service map is created by mapping the relationships among various applications, application services, and infrastructure elements.
Note: If you're in a Dynatrace-managed (self‑hosted) or legacy SaaS environment, you should use the Service Graph Connector for Observability - Dynatrace.
- Accurately classifies Dynatrace data into the Applications, Application Services, and Servers CI classes.
- Automatically builds and maintains service maps and relationships across CIs, enabling accurate topology visibility and downstream impact analysis.
- Helps correlate Dynatrace events to the correct CIs in the CMDB, delivering context-rich insights that enable accurate incident routing.
- New
- The following new Kubernetes entities are ingested into the CMDB: Container, Cluster, Namespace, Node, Pod, Service, and Workload.
- Kubernetes data sources can now run on their own schedule, decoupled from the Host job, so Kubernetes data can be pulled at a different and more frequent cadence than core entities data.
- Kubernetes data sources use a new, configurable, hours-based initial-fetch window (default: 2 hours) for the first sync, preventing large historical pulls on the initial run.
- Kubernetes payloads that exceed the platforms inline processing limit (observed up to ~132 MB) can be now saved as an attachment, preventing import failures in large Kubernetes environments.
- Kubernetes labels and annotations are now imported and preserved as CI tags.
- A new SGC Central activity step is available for migrating from the Classic connector to the new connector.
- Kubernetes Pods and Containers are automatically marked absent in CMDB.
- Changed
- Hosts, Processes, Frontends, and Services from Dynatrace are now automatically marked as retired based on the last seen window from Dynatrace. This window can be configured in the ci_retirement_threshold_days connection property.
- Process CI reconciliation against Discovery has been improved across DB2, MSSQL, Apache, NGINX, IIS, and PostgreSQL, reducing duplicate process CIs.
- Fixed
- The connector now links existing VM CIs to their Server CI using object ID matching, instead of creating a duplicate VM CI.
- Dynatrace DQL query is optimized to improve overall data loading performance.
Required plugins and products:
- Integration Commons for CMDB (from ServiceNow Store)
- CMDB CI Class Model (from ServiceNow Store)
- ITOM Discovery License
- IntegrationHub Data Stream Action
The use of this Service Graph Connector requires a subscription to a Subscription Unit-based IT Operations Management (ITOM) Visibility or ITOM Discovery application. Managed IT Resources (as defined in Section 1.1 of the ServiceNow Subscription Unit Overview - https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/servicenow-subscription-unit-overview.pdf) created or modified in the CMDB by this Service Graph Connector, but not yet managed by ITOM Visibility or ITOM Discovery, will increase Subscription Unit consumption within that application. Customers should review their current Subscription Unit consumption within ITOM Visibility or ITOM Discovery to ensure available capacity.