{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":49261,"path":"servicenow-platform/service-graph-connectors/sgcc-configure-dynatrace.md","title":"Configure Service Graph Connector for Observability - Dynatrace using SGC Central","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure Service Graph Connector for Observability - Dynatrace using SGC Central\n\nSet up scheduled import jobs to pull in Dynatrace data into your Configuration Management Database \\(CMDB\\).\n\n## Before you begin\n\n**Important:** The Service Graph Connector for Observability - Dynatrace supports Dynatrace Classic \\(v1/v2 APIs\\) and is intended for Dynatrace managed \\(self‑hosted\\) or legacy SaaS environments. If you're using or upgrading to the latest Dynatrace 3rd-generation SaaS platform, you should use the new Service Graph Connector for Observability - Dynatrace SaaS.\n\nInstall Service Graph Connector for Observability - Dynatrace version 1.11.0 or later 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).\n\nRole required: The following table shows the roles required for each stage of the playbook.\n\n|Stage|Role|\n|-----|----|\n|Prerequisites|admin|\n|Setup|SGC-Admin \\(sn\\_cmdb\\_int\\_util.sgc\\_admin\\) or admin|\n\n**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).\n\n## About this task\n\nThe playbook experience for onboarding connectors is activated with SGC Central in the Service Graph Workspace or 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.\n\n## Procedure\n\n1.  Use one of the following methods to open SGC Central:\n\n    -   Navigate to **Workspaces** &gt; **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.\n    -   Navigate to **Workspaces** &gt; **CMDB Workspace** &gt; **SGC Central**.\n2.  On the Overview page, select **Create connection**.\n\n    **Tip:** Alternatively, you can select **Create connection** on the All connections page.\n\n3.  On the Create connection window, select the Dynatrace connector type, and then select **Configure connection**.\n\n4.  Complete the initial prerequisites when setting up a connection for the first time using a connector.\n\n    1.  Install the Observability Commons for CMDB application \\(sn\\_observability\\) for event ingestion.\n\n        **Note:** The **Install Observability Commons for CMDB** activity appears only when the Observability Commons for CMDB application \\(sn\\_observability\\) isn't already installed. If event ingestion isn't needed, you can skip this step by selecting **Continue** for the **Install Observability Commons for CMDB** activity.\n\n        1.  In the **Prerequisites** stage of the playbook, select the **Install Observability Commons for CMDB** activity.\n        2.  Install the [Observability Commons for CMDB](https://store.servicenow.com/sn_appstore_store.do#!/store/application/97e04562072020107add6a77c4a9351a) application \\(sn\\_observability\\) from the ServiceNow Store.\n        3.  After you have installed the application, select **Continue**.\n    2.  Create data sources for the connection.\n\n        **Note:** This step is required when configuring the connector for the first time only.\n\n        1.  Verify that you have edit permissions for the Datasource \\[sys\\_data\\_source\\] table.\n        2.  In the **Prerequisites** stage of the playbook, select the **Update data source access** activity.\n        3.  Select **Update access**.\n        4.  To edit the record, select the **Global** application scope from the application picker.\n        5.  In the Application Access related list of the Data Source form, select the **Can create**, **Can update**, and **Can delete** check boxes.\n        6.  Select **Update**.\n        7.  From the application picker, select the application scope of the connector.\n        8.  After completing the **Update data source access** activity, select **Continue**.\n    3.  Enable creating scheduled jobs for the connection by updating the scheduled data import access.\n\n        **Note:** This step is required when configuring the connector for the first time only.\n\n        1.  Verify that you have edit permissions for the Scheduled Data Import \\[scheduled\\_import\\_set\\] table.\n        2.  In the **Prerequisites** stage of the playbook, select the **Update scheduled data import access** activity.\n        3.  Select **Update access**.\n        4.  To edit the record, select the **Global** application scope from the application picker.\n        5.  In the Application Access related list of the Data Source form, select the **Can create**, **Can update**, and **Can delete** check boxes.\n        6.  Select **Update**.\n        7.  From the application picker, select the application scope of the connector.\n        8.  After completing the **Update scheduled data import access** activity, select **Continue**.\n    4.  Enable creating values for the connection by updating the variable value access.\n\n        **Note:** This step is required when configuring the connector for the first time only.\n\n        1.  Verify that you have edit permissions for the Value \\[sys\\_variable\\_value\\] table.\n        2.  In the **Prerequisites** stage of the playbook, select the **Update variable value access** activity.\n        3.  Select **Update access**.\n        4.  To edit the record, select the **Global** application scope from the application picker.\n        5.  In the Application Access related list of the Data Source form, select the **Can create**, **Can update**, and **Can delete** check boxes.\n        6.  Select **Update**.\n        7.  From the application picker, select the application scope of the connector.\n        8.  After completing the **Update variable value access** activity, select **Continue**.\n    5.  Clear the cache on the Data Source \\[sys\\_data\\_source\\] table.\n\n        **Note:** This step is required when configuring the connector for the first time only.\n\n        1.  In the **Prerequisites** stage of the playbook, select the **Clear cache** activity.\n        2.  Select **Run clear cache**.\n        3.  In the **Run script** text box of the background script page, enter the following script:\n\n            ```\n            GlideTableManager.invalidateTable(\"sys_data_source\");\n                  GlideCacheManager.flushTable(\"sys_data_source\");\n            \n                  GlideTableManager.invalidateTable(\"scheduled_import_set\");\n                  GlideCacheManager.flushTable(\"scheduled_import_set\");\n            \n                  GlideTableManager.invalidateTable(\"sys_variable_value\");\n                  GlideCacheManager.flushTable(\"sys_variable_value\");\n            \n                  GlideTableManager.invalidateTable(\"sys_db_object\");\n                  GlideCacheManager.flushTable(\"sys_db_object\");\n            ```\n\n        4.  Select **Run Script** to run the background script in the **global** scope.\n\n            The script may take several minutes to execute.\n\n        5.  After the script is executed, select **Close**.\n        6.  From the application picker, select the application scope of the connector.\n        7.  After completing the **Clear cache** activity, select **Continue**.\n    6.  Verify that the Event Management application works properly with the Dynatrace environment by copying the `EvtMgmtImpactManagerMediator` script to the Global application scope.\n\n        **Note:** This step is displayed only when the Observability Commons for CMDB plugin \\(sn\\_observability\\) is already installed and is required when configuring the connector for the first time only.\n\n        1.  In the **Prerequisites** stage of the playbook, select the **Enable script access for event management** activity.\n        2.  Select **Enable script access**.\n        3.  Select the **Global** application scope from the application picker.\n        4.  From the context menu, select **Insert and Stay**.\n        5.  Verify that the `EvtMgmtlmpactManagerMediator` script was copied to the Global application scope and the **Accessible from** field was set to `All application scopes`.\n        6.  Select **Update**.\n        7.  From the application picker, select the application scope of the connector.\n        8.  After completing the **Enable script access for event management** activity, select **Continue**.\n5.  Enter connection details and test the API connection for importing Dynatrace data.\n\n    1.  In the **Setup** stage of the playbook, select the **Create and test connection** activity.\n\n    2.  On the form, fill in the fields.\n\n<table id=\"table_ahn_xtg_rmb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nConnection name\n\n</td><td>\n\nName to identify the Dynatrace connection record.\n\n</td></tr><tr><td>\n\nHostname\n\n</td><td>\n\nHostname of your Dynatrace environment.\n\n</td></tr><tr><td>\n\nAPI Key\n\n</td><td>\n\nDynatrace API Key.**Note:** The API Key must be prefixed with `api-token`.\n\n</td></tr></tbody>\n</table>    3.  Select **Create and test connection**.\n\n    4.  Once the connection test is complete, select **Continue**.\n\n6.  Configure the connection and connector properties to map attributes and manage data imports.\n\n    **Note:** To skip this step, select **Continue** for the **Set configuration properties** activity.\n\n    1.  In the **Setup** stage of the playbook, select the **Set configuration properties** activity.\n\n    2.  Fill in the form.\n\n<table id=\"table_orp_332_4yb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nManagement zone Ids\n\n</td><td>\n\nList of the management zone IDs to fetch from your Dynatrace environment. For multiple entries, separate the zone IDs with commas.\n\n</td></tr><tr><td>\n\nManagement zone names\n\n</td><td>\n\nList of the management zones to fetch from your Dynatrace environment. For multiple entries, separate the zone names with commas.\n\n</td></tr><tr><td>\n\nService types\n\n</td><td>\n\nList of the Dynatrace service types from where to ingest the data into the CMDB. For multiple entries, separate the service types with commas.**Note:** All service types except for DATABASE\\_SERVICE are mapped to the Calculated Application Service \\[cmdb\\_ci\\_service\\_calculated\\] CMDB table. The DATABASE\\_SERVICE service type is mapped to the Database Instance \\[cmdb\\_ci\\_db\\_instance\\] CMDB table.\n\nValid values are:\n\n-   BACKGROUND\\_ACTIVITY\n-   CICS\\_SERVICE\n-   CUSTOM\\_SERVICE\n-   DATABASE\\_SERVICE\n-   ENTERPRISE\\_SERVICE\\_BUS\\_SERVICE\n-   EXTERNAL\n-   IBM\\_INTEGRATION\\_BUS\\_SERVICE\n-   IMS\\_SERVICE\n-   MESSAGING\\_SERVICE\n-   QUEUE\\_LISTENER\\_SERVICE\n-   RMI\\_SERVICE\n-   RPC\\_SERVICE\n-   WEB\\_REQUEST\\_SERVICE\n-   WEB\\_SERVICE\n\n\n</td></tr><tr><td>\n\nTags\n\n</td><td>\n\nList of the tag names to fetch from your Dynatrace environment. For multiple entries, separate the tags with commas.\n\n</td></tr></tbody>\n</table>    3.  To manage data source failures during import, select the **Save REST response as attachment** check box to save each response as an attachment temporarily.\n\n    4.  Select **Continue**.\n\n7.  To enable Dynatrace notifications as events in your ServiceNow instance, trigger the workflow to create a problem notification and alerting profile in your Dynatrace environment.\n\n    **Note:** This step is displayed only when the Observability Commons for CMDB plugin \\(sn\\_observability\\) is already installed. To skip this step, select **Skip** for the **Configure observability** activity.\n\n    1.  In the **Setup** stage of the playbook, select the **Configure observability** activity.\n\n    2.  Select **Create problem notification**.\n\n        **Note:** The created records appear in the Dynatrace application under the display name `ServiceNow default Problem notification` and can be customized.\n\n    3.  Dismiss any success alerts and select **Continue**.\n\n8.  Configure the import schedule to import data at regular intervals.\n\n    1.  In the **Setup** stage of the playbook, select the **Configure import schedule** activity.\n\n    2.  Expand the Parent scheduled data import within the Import schedules list to select the **SGO-Dynatrace Hosts - _Connection Name_** import schedule.\n\n    3.  Select the **Active** check box, and then fill in the run schedule and time details.\n\n        For more information, see [Schedule a data import](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/integrate-applications/t_ScheduleADataImport.md#table_r53_5hm_xp).\n\n    4.  Select **Save**.\n\n        Alternatively, select **Execute Now** to execute the import schedule immediately.\n\n    5.  Select **Continue**.\n\n9.  In the **Setup** stage of the playbook, select the **Confirm connection creation** activity to verify whether the connection was created.\n\n\n## What to do next\n\nSelect **View all connections** to review the connection details. The created connection appears in the Installed connections list.\n\n**Related topics**  \n\n\n[Service Graph Connector for Observability - Dynatrace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-graph-connectors/cmdb-integration-dynatrace.md)\n\n[CMDB classes targeted in Service Graph Connector for Observability - Dynatrace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-graph-connectors/cmdb-dynatrace-classes.md)\n\n[Service Graph Connector for Observability - Dynatrace properties](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/servicenow-platform/service-graph-connectors/sgc-cmdb-dynatrace-props.md)\n\n"}}