Skip to content
Release: Australia · Updated: 2026-07-07 · Official documentation · View source

Data mapping for Service Graph Connector for Observability - Dynatrace SaaS

Data from the Dynatrace data sources is mapped and transformed into the ServiceNow CMDB Configuration Item (CI) class definitions using the Robust Transform Engine (RTE). Data is inserted into the ServiceNow 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 Dynatrace.

Important: The Service Graph Connector for Observability - Dynatrace SaaS is designed for the Dynatrace SaaS (3rd‑generation) platform and leverages DQL-based APIs and the Grail architecture to import data from Dynatrace into the CMDB. If you're in a Dynatrace managed (self‑hosted) or legacy SaaS environment, you should use the Service Graph Connector for Observability - Dynatrace.

The following table lists the data sources, the staging tables, and the target tables as CMDB CI classes for Dynatrace.

Data sourceStaging tableTarget tablesNotes
SGO-Dynatrace SaaS FrontendSGO-Dynatrace SaaS Frontend \[sn\_dynatrace\_saas\_sgo\_dynatrace\_saas\_frontend\]Calculated Application Service-
SGO-Dynatrace SaaS HostSGO-Dynatrace SaaS Host \[sn\_dynatrace\_saas\_sgo\_dynatrace\_saas\_host\]Computer IP Address Serial Number Key Value When the Software Asset Management \(SAM\) application isn't installed: - Software - Software Instance When the SAM application is installed: Software InstallationHost classification: Depending on the operating system \(OS\), data is imported into the Linux Server \[cmdb\_ci\_linux\_server\], Windows Server \[cmdb\_ci\_win\_server\], AIX Server \[cmdb\_ci\_aix\_server\], or Solaris Server \[cmdb\_ci\_solaris\_server\] classes. For other OS types, the data is imported into the Computer \[cmdb\_ci\_computer\] class.
SGO-Dynatrace SaaS ProcessesSGO-Dynatrace SaaS Processes \[sn\_dynatrace\_saas\_sgo\_dynatrace\_saas\_processes\]ApplicationThe target table is populated using Application Dependency Mapping \(ADM\). ADM classifies the processes based on the attributes in the Process Classification \[discovery\_classy\_proc\] table. To learn about process classification, see Discovery classifiers.
SGO-Dynatrace SaaS ServiceSGO-Dynatrace SaaS Service \[sn\_dynatrace\_saas\_sgo\_dynatrace\_saas\_service\]Calculated Application Service-
SGO-Dynatrace Classic Migration CleanupSGO-Dynatrace Classic Migration Cleanup \[sn\_dynatrace\_saas\_sgo\_dynatrace\_classic\_migration\_cleanup\]ApplicationOne-time cleanup of stale process CIs \(after migration\) originally ingested by the Dynatrace Classic connector \(SGO-Dynatrace\).​ See dynatrace_classic_connection_alias_sys_id connection property.
SGO-Dynatrace SaaS CI RetirementSGO-Dynatrace SaaS CI Retirement \[sn\_dynatrace\_saas\_sgo\_dynatrace\_saas\_ci\_retirement\]ApplicationAutomatically retire stale CIs that aren't seen for a configurable threshold. See ci_retirement_threshold_days connection property.

You can use the IntegrationHub ETL app to view the data maps. See IntegrationHub ETL for more information.