--- title: Configure Service Graph Connector for Dynatrace SaaS using SGC Central description: Use the playbook in SGC Central to set up the Service Graph Connector for Dynatrace SaaS and pull Dynatrace data into your CMDB. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/servicenow-platform/service-graph-connectors/sgcc-configure-dynatrace-saas.html release: australia product: Service Graph Connectors classification: service-graph-connectors topic_type: task last_updated: "2026-06-03" reading_time_minutes: 4 breadcrumb: [Observability - Dynatrace SaaS, Service Graph Connectors, Integrating third-party data into CMDB, Configuration Management, Extend ServiceNow AI Platform capabilities] --- # Configure Service Graph Connector for Dynatrace SaaS using SGC Central Use the playbook in SGC Central to set up the Service Graph Connector for Dynatrace SaaS and pull Dynatrace data into your CMDB. ## Before you begin **Important:** The Service Graph Connector for 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. Install Service Graph Connector for Dynatrace SaaS from the ServiceNow Store. For ServiceNow Store installation steps, see [Install a ServiceNow Store application](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/installing-applications-in-application-manager.md). Role required: The following table shows the roles required for each stage of the playbook. |Stage|Role| |-----|----| |Prerequisites|admin| |Setup|SGC-Admin \(sn\_cmdb\_int\_util.sgc\_admin\) or admin| **Note:** The admin user role is required to run background scripts and to provide access to global tables to the SGC-Admin user. For information about the user roles for Service Graph Connectors, see [Service Graph Connector user roles](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/configuration-management-database-cmdb/cmdb-sgc-intro.md). ## About this task The playbook experience for onboarding connectors is activated with SGC Central in the CMDB Workspace. To configure the SGC Central application, see [Configuring SGC Central](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/sgcc-configuring.md) and for more information on how to interact with a playbook, see Interact with Playbook. ## Procedure 1. Use one of the following methods to open SGC Central: - Navigate to **Workspaces** > **Service Graph Workspace**, and from the left navigation panel, select the Ingestion icon \[Omitted image "icon-sgc-central.png"\] to open the SGC Central view. - Navigate to **Workspaces** > **CMDB Workspace** > **SGC Central**. 2. On the Overview page, select **Create connection**. 3. On the Create connection window, select the Dynatrace SaaS connector type, and then select **Create connection**. 4. Complete the initial prerequisites when setting up a connection for the first time. **Note:** This step is required only during the first-time setup. See [Perform initial setup tasks when creating a connection in SGC Central](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/sgcc-first-time-setup.md). 5. Enter connection details and test the connection for importing Dynatrace data. 1. In the **Setup** stage, select **Create and test connection**. 2. On the form, fill in the fields.
| Field | Description |
|---|---|
| Connection name | Name to identify the Dynatrace SaaS connection record. |
| Hostname | Host name of your Dynatrace environment \(`*Dynatrace-tenant*.apps.dynatrace.com`\). |
| Platform Token | Dynatrace platform token \(see [Platform tokens](https://docs.dynatrace.com/docs/manage/identity-access-management/access-tokens-and-oauth-clients/platform-tokens)\).**Note:** The platform token must not be prefixed with `Bearer`. |