1. Select Configure.
2. Switch to the global scope.
3. Select the Additional actions icon ().
4. Select Insert and Stay.
5. Select Mark as Complete.

1. Select Configure.
2. Select the EvtMgmtImpactManagerMediator script and verify it was copied to the global scope.
3. In the Accessible from field, ensure it is set to All application scopes.
4. Select Mark as Complete.

1. Select Configure.
2. In the API Key field, enter api-token <your api token>.

   For example, api-token mytokenid.

3. Select Mark as Complete.

1. Select Configure.
2. Update the Host field with a fully qualified hostname for your Dynatrace instance.

   For example, abc123.live.dynatrace.com.

   The hostname is automatically filled in the Connection URL field.

3. Enable the use of a MID Server, select the Use MID Server check box.
   Hinweis:

   The HTTP connection will be pre-configured to use the API key that was configured during the previous setup task.
4. Select Mark as Complete.

1. In the Test Connection section, select Configure.
2. To test the connection configuration, select Test Connection.
   Hinweis:

   If any of the tests have errors, follow the suggestions for remediation.
3. Set the Test Connection task to complete by selecting Mark as Complete.

1. Update the name of the payload template, if needed.
2. Select Problem Notification Setup.
3. Set the Create Default Notification Payload Template task to complete by selecting Mark as Complete.

1. In the Run script text box of the background script page, enter the following script:

   var gr = new GlideRecord("sys_object_source");
   gr.addQuery("name", "SGO-Dynatrace");
   var grOR = gr.addQuery("id", "STARTSWITH", "HOST-");
   grOR.addOrCondition("id", "STARTSWITH", "PROCESS_GROUP_INSTANCE-");
   grOR.addOrCondition("id", "STARTSWITH", "PROCESS_GROUP-");
   grOR.addOrCondition("id", "STARTSWITH", "SERVICE-");
   grOR.addOrCondition("id", "STARTSWITH", "APPLICATION-");
   gr.query();
   while (gr.next()) {
       gr.setValue("id", "f379137e075820107add6a77c4a93538|||" + gr.getValue("id"));
       gr.update();
   }

2. Select Run Script to run the background script in the global scope.

   The script may take several minutes to execute.

3. After the script is executed, select Close.
4. From the application picker, select the Service Graph Connector for Observability Dynatrace application.
5. Select Mark as Complete.

1. In the Configure Dynatrace Grail OAuth section of the Service Graph Connector for Observability Dynatrace Setup page, select Get Started.
2. For the Set Dynatrace Grail status task, select Configure and review or modify the property settings for a Grail-enabled tenant.
3. If you've Grail-enabled tenant, set the Value field of the grailEnabled property to true.

   Else, leave the value set to false.

4. Set the Configure Dynatrace Grail OAuth task to complete by selecting Mark as Complete.

1. In the Configure OAuth credentials section, select Configure.
2. On the Workflow Studio page that opens in a new browser tab, select Add Connection.
3. Enter a name, the connection URL, OAuth client ID, and OAuth client secret details.
4. Select Create and Get OAuth Token.
5. Return to the guided setup page.
6. Set the Configure OAuth credentials task to complete by selecting Mark as Complete.

1. In the Test Connection section, select Configure.
2. To test the connection configuration, select Test Connection.
3. When the Status field is set to Success, select Update to close the Test the connection dialog box and return to the guided setup page.

   If any of the tests have errors, follow the suggestions for remediation.

4. Set the Test Connection task to complete by selecting Mark as Complete.

• Review the page size used in REST API requests to fetch Dynatrace entities.
• Define number of days a configuration item (CI) can be inactive before it is ignored.
• Enter the percentage of an application cluster's nodes that need to be in a state to raise that state to its parent in the service map.

  For example, you can define the percentage of nodes that need to go critical for the parent of a cluster to be in a critical state. If there are 10 nodes in a cluster, setting the property value to 70 would require at least 7 out of the 10 nodes in the cluster to go into a critical state to reflect up to the parent service of the cluster.

• Enable ingesting events that do not have a matching CI in the CMDB.
• Enable populating the Application (cmdb_ci_appl) CIs from Dynatrace (Dynatrace processes) during scheduled imports.

1. In the Configure Instance Settings section, select Configure.
2. In the Service Graph Connection Properties related list, configure the properties of the connection record.

   Tabelle : 1. Dynatrace connection properties

   Property	Description
   managementZoneNames	Enter the name of the management zone to fetch from your Dynatrace environment. For multiple entries, separate the zone names with commas.
   tags	Enter the name of the tags to fetch from your Dynatrace environment. For multiple entries, separate the tags with commas.
   serviceTypes	Enter the list of Dynatrace service types from where to ingest the data into CMDB. For multiple entries, separate the service types with commas. Hinweis: 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. Valid values are: BACKGROUND_ACTIVITY CICS_SERVICE CUSTOM_SERVICE DATABASE_SERVICE ENTERPRISE_SERVICE_BUS_SERVICE EXTERNAL IBM_INTEGRATION_BUS_SERVICE IMS_SERVICE MESSAGING_SERVICE QUEUE_LISTENER_SERVICE RMI_SERVICE RPC_SERVICE WEB_REQUEST_SERVICE WEB_SERVICE
   managementZoneIds	Enter the management zone ID to fetch from your Dynatrace environment. For multiple entries, separate the zone IDs with commas.

3. Select Update.
4. Complete the Configure Instance Settings task by selecting Mark as Complete.

The setup enables pulling ITOM events from Dynatrace into the ServiceNow instance.

1. In the Configure Problem Notification section, select Configure.
2. To push the configuration to Dynatrace, select Problem Notification Setup.
3. To receive the configuration from Dynatrace, select Fetch Notification Setup.
4. Complete the Configure Problem Notification task by selecting Mark as Complete.

1. Select Configure.
2. In the State field, wait for the field to change to Complete or Complete with errors.

   It is normal to have errors during the migration from an older version.

3. To refresh the list, select and hold (or right-click) the header and select Refresh List.
4. Select Mark as Complete.

1. Select Configure.
2. Change the current scope to Global.
3. Select the menu icon ().
4. Select Insert and Stay.
5. Select Mark as Complete.

1. Select Configure.
2. Select the record of the script you copied.
3. Select Update.

1. Ensure that you have edit permissions for the Datasource [sys_data_source] table.
2. For the Update Data Source Access task, select Configure.
3. To edit the record, select the Global application scope from the application picker.
4. In the Application Access related list of the Data Source form that opens in a new tab, select the Can create, Can update, and Can delete check boxes.
5. Select Update to return to the guided setup page.
6. Select the Service Graph Connector for Observability Dynatrace application scope from the application picker.
7. Set the Update Data Source Access task to complete by selecting Mark as Complete.

1. Ensure that you have edit permissions for the Scheduled data import [scheduled_import_set] table.
2. For the Update Scheduled Data Import Access task, select Configure.
3. To edit the record, select the Global application scope from the application picker.
4. In the Application Access related list of the Data Source form that opens in a new tab, select the Can create, Can update, and Can delete check boxes.
5. Select Update to return to the guided setup page.
6. Select the Service Graph Connector for Observability Dynatrace application scope from the application picker.
7. Set the Update Scheduled Data Import Access task to complete by selecting Mark as Complete.

1. Ensure that you have edit permissions for the Value [sys_variable_value] table.
2. For the Update Value Access task, select Configure.
3. To edit the record, select the Global application scope from the application picker.
4. In the Application Access related list of the Data Source form that opens in a new tab, select the Can create, Can update, and Can delete check boxes.
5. Select Update to return to the guided setup page.
6. Select the Service Graph Connector for Observability Dynatrace application scope from the application picker.
7. Set the Update Value Access task to complete by selecting Mark as Complete.

1. For the Clear Cache for Datasource and Import set task, select Configure.
2. In the Run script text box of the background script page, enter the following script:

   
         GlideTableManager.invalidateTable("sys_data_source");
         GlideCacheManager.flushTable("sys_data_source");
   
         GlideTableManager.invalidateTable("scheduled_import_set");
         GlideCacheManager.flushTable("scheduled_import_set");
   
         GlideTableManager.invalidateTable("sys_variable_value");
         GlideCacheManager.flushTable("sys_variable_value");
   
         GlideTableManager.invalidateTable("sys_db_object");
         GlideCacheManager.flushTable("sys_db_object");

3. Select Run Script to run the background script in the global scope.

   The script may take several minutes to execute.

4. After the script is executed, select Close.
5. Select the Service Graph Connector for Observability Dynatrace application scope from the application picker.
6. Set the Clear Cache for Datasource and Import set task to complete by selecting Mark as Complete.

1. Ensure that the application scope is set to Service Graph Connector for Observability in the application picker.
2. For the Add Another Connection task, select Configure.
3. On the Workflow Studio page that opens in a new browser tab, select Add Connection.
4. On the form, fill in the fields.

   Tabelle : 2. Connection form

   Field	Description
   Connection Name	Display name for the connection.
   Connection Hostname	Host name of the Dynatrace instance.
   API Key	Dynatrace API Key. Hinweis: The API Key must be prefixed with api-token.

5. Select Create Connection.
6. Return to the guided setup page.
7. Set the Add Another Connection task to complete by selecting Mark as Complete.

1. For the Add another OAuth connection task, select Configure.
2. On the Workflow Studio page that opens in a new browser tab, select Add Connection.
3. Enter a name, the connection URL, OAuth client ID, and OAuth client secret details.
4. Select Create and Get OAuth Token.
5. Return to the guided setup page.
6. Set the Add another OAuth connection task to complete by selecting Mark as Complete.

1. For the Link connection record with OAuth client credentials task, select Configure.
2. In the OAuth 2.0 Connection and Credentials Alias field, search for and select the OAuth connection alias you created in the step 9.g.
3. In the Service Graph connection record, search for and select the connection record you created in step 9.f.
4. Select Submit.
5. Return to the guided setup page.
6. Set the Link connection record with OAuth client credentials task to complete by selecting Mark as Complete.

1. For the Configure Mid Servers task, select Configure.
2. Select the name of the connection you created.
3. Select the Use MID server check box.
4. Select Update.
5. Set the Configure Mid Servers task to complete by selecting Mark as Complete.

1. In the Configure Instances section, select Configure.
2. Select the name of the connection you want to configure and then select Update.
3. Set the Configure Instances task to complete by selecting Mark as Complete.

1. For the Test Connections task, select Configure.
2. Select the name of the connection you want to test.
3. To validate the data source configuration, select Test Load 20 Records.
4. When the Status field is set to Success, select Update to close the Test the connection dialog box and return to the guided setup page.

   If any of the tests have errors, follow the suggestions for remediation.

5. Set the Test Connections task to complete by selecting Mark as Complete.

1. Ensure that you have the access token with the following scopes:
   • Read configuration (ReadConfig)
   • Write configuration (WriteConfig)
   • Read log content (LogExport)
   • Read metrics (metrics.read)
2. For the Create Default Notification Payload Templates task, select Configure.
3. Select the connection you want to create a default notification payload template for.
4. Update the name of the payload template, if needed.
5. Select Problem Notification Setup.
   The notification is created with the payload parameters as described in the following table.

   Tabelle : 3. Notification payload paramters

   Parameter	Description
   name	Name of the notification. The name is automatically prefixed with ServiceNow Default Problem Notification and the instance name is added to it.
   alertingProfile	ID of the alerting profile in Dynatrace.
   type	Type of payload that is automatically set to webhook.
   url	Webhook URL in the format https://https://<instance name>.service-now.com/ /api/sn_em_connector/em/inbound_event?source=SGO-Dynatrace.
   payload	Custom payload created for notification in the following format: { "ImpactedEntities": {ImpactedEntities}, "ImpactedEntity": "{ImpactedEntity}", "PID": "{PID}", "ProblemDetailsHTML": "{ProblemDetailsHTML}", "ProblemDetailsJSON": {ProblemDetailsJSON}, "ProblemDetailsMarkdown": "{ProblemDetailsMarkdown}", "ProblemDetailsText": "{ProblemDetailsText}", "ProblemID": "{ProblemID}", "ProblemImpact": "{ProblemImpact}", "ProblemSeverity": "{ProblemSeverity}", "ProblemTitle": "{ProblemTitle}", "ProblemURL": "{ProblemURL}", "State": "{State}", "Tags": "{Tags}" }

6. Repeat the steps for each connection.
7. Set the Create Default Notification Payload Templates task to complete by selecting Mark as Complete.

For more information, see Schedule a data import.