--- sourceDocument: Store Version History Release Notes sourceDocumentLink: https://www.servicenow.com/docs/r/store-release-notes Release : - store ft:locale : - en-US ft:publication_title : - Store Version History Release Notes ft:clusterId : - rnst bundleId : - rnst --- # Service Graph Connector for Observability - Dynatrace SaaS release notes # Service Graph Connector for Observability - Dynatrace SaaS release notes {#ariaid-title1} Release version: Store Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Service Graph Connector for Observability - Dynatrace SaaS release notes The Service Graph Connector for Observability - Dynatrace SaaS integrates data from the Dynatrace SaaS platform into ServiceNow's Configuration Management Database (CMDB). It utilizes DQL-based APIs and the Grail architecture to import and map infrastructure and application data, enabling enhanced visibility of service topologies within ServiceNow. Show full answer Show less This connector is specifically designed for the Dynatrace SaaS (3rd-generation) environment. For customers using Dynatrace-managed (self-hosted) or legacy SaaS environments, the original Service Graph Connector for Observability - Dynatrace should be used instead. ## Key Features * **Version 1.2.0 (September 2026):** * Introduces ingestion of new Kubernetes entities into the CMDB, including Container, Cluster, Namespace, Node, Pod, Service, and Workload. * Kubernetes data sources can run on independent schedules, allowing more frequent data pulls separate from Host data. * Configurable initial fetch window for Kubernetes data to avoid large historical data imports on first sync (default 2 hours). * Large Kubernetes payloads exceeding platform limits can now be saved as attachments to prevent import failures. * Kubernetes labels and annotations are imported and preserved as Configuration Item (CI) tags. * New migration activity step to assist moving from the Classic connector to the new connector. * Automatic marking of Kubernetes Pods and Containers as absent in CMDB when appropriate. * Hosts, Processes, Frontends, and Services from Dynatrace are automatically retired based on a configurable last-seen threshold. * Improved process CI reconciliation with Discovery data for major technologies (DB2, MSSQL, Apache, NGINX, IIS, PostgreSQL), reducing duplicates. * Fixes to prevent duplicate VM CIs by linking existing VMs to Server CIs via object ID matching. * Optimized Dynatrace DQL queries for better data loading performance. * **Version 1.1.0 (July 2026):** * Introduced segment-based configuration for imported Dynatrace entities, replacing management zone filtering. * Automatic retirement of CIs not observed within a configurable staleness threshold. * Cleanup script available to retire stale process CIs from the Classic connector. * Front-end entities are linked to dependent services to enhance service topology visibility. * Process CI names aligned with ServiceNow Discovery conventions for several technologies. * Improved reconciliation accuracy for WebSphere process CIs by including cell and node attributes. * Default filtering of containerized processes to reduce duplicate Application CIs. * Normalization of Windows process paths to avoid duplicate Application CIs. * **Version 1.0.0 (June 2026):** * Initial release supporting import of Hosts, Processes, Services, and Frontends from Dynatrace SaaS into the CMDB. * Creates service maps by mapping relationships among applications, services, and infrastructure. ## Practical Benefits for ServiceNow Customers * Enhanced visibility into Kubernetes and Dynatrace-managed infrastructure and applications within ServiceNow CMDB. * Improved data synchronization flexibility and performance with independent scheduling and optimized queries. * Reduced CI duplication and improved data accuracy through enhanced reconciliation and normalization. * Automated lifecycle management of CIs with configurable retirement based on data staleness. * Simplified migration path from the Classic Dynatrace connector to the new SaaS connector. Version history for the ServiceNow® Service Graph Connector for Observability - Dynatrace SaaS application on the ServiceNow Store. Important: For details on system requirements and family compatibility, view the application listing on the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website. ## Version history Version 1.2.0 - September 2026 : * 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. {#store-cmdb-rn-sgc-observability-dynatrace-saas__ul_vpr_vgq_lkc} * 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. {#store-cmdb-rn-sgc-observability-dynatrace-saas__ul_vhx_vgq_lkc} Version 1.1.0 - July 2026 : * New: * The Dynatrace entities that are to be imported are configured using segment, replacing management zone filtering from the Classic connector. * CIs that aren't observed by Dynatrace within a configurable staleness threshold are automatically retired. * The classic connector migration cleanup script can be used to retire stale process CIs created by the Dynatrace Classic connector. * Front-end entities are now mapped to their dependent services, improving service topology visibility in ServiceNow. * Changed: * Process CI names are aligned with ServiceNow Discovery conventions for MSSQL, NGINX, Apache, IIS, and WebSphere. * WebSphere process CIs include cell and node attributes, improving reconciliation accuracy against Discovery data. * Containerized processes are filtered out by default to reduce duplicate Application CIs. * Path separator and formatting inconsistencies in Windows process paths are normalized, reducing duplicate Application CIs. {#store-cmdb-rn-sgc-observability-dynatrace-saas__ul_y3j_tmd_tjc} Version 1.0.0 - June 2026 : * 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.