How do I configure integration between ServiceNow ITSM/ITOM and Dynatrace?

Dynatrace offers an out-of-the-box integration with ServiceNow. Once configured, Dynatrace auto-discovered problems—along with all related real-user and root-cause data—are automatically pushed to your ServiceNow instance. All uncorrelated events related to each Dynatrace-detected problem are sent to the ServiceNow ITOM events table (em_event). Optionally, Dynatrace can also synchronize all auto-discovered applications, services, and hosts with your ServiceNow CMDB database.

Dynatrace ServiceNow integration is a two-way integration that:

  1. Pushes incidents from your Dynatrace environment to your ServiceNow tenant.
  2. (Optionally) pushes all single events of a detected problem to the ServiceNow ITOM event API
  3. Pulls host, process, service, and application information from Dynatrace through a scheduled job within your ServiceNow instance.

To connect your Dynatrace monitoring environment with your ServiceNow instance, configuration is required on both the ServiceNow and the Dynatrace side.

Open the ServiceNow application marketplace and install the ServiceNow-certified Dynatrace application (shown below) within your ServiceNow instance. The Dynatrace application is certified for the following ServiceNow releases: Istanbul, Jakarta, and Kingston.

Once you've installed the Dynatrace application within your ServiceNow instance, you’ll find a new Dynatrace menu in ServiceNow with the following entries:

  • Support: Links directly to Dynatrace Support, where you can report any issues related to your Dynatrace ServiceNow integration
  • Dynatrace Settings: Use these settings to configure your Dynatrace integration.
  • Environments: Configure one or multiple Dynatrace monitoring environments and token credentials to synchronize CMDB information from.
  • Problems: Import set table that shows the number of Dynatrace-detected problems that have been pushed to and imported into your incident table.
  • Applications and services: A filtered view of your CMDB business service table that shows all the services and applications that have been discovered by Dynatrace.
  • Process groups: A filtered view of your CMDB cluster table that shows all Dynatrace-discovered process group clusters.
  • Hosts: A filtered view of your CMDB servers table that shows all Dynatrace-discovered hosts.
  • CI Mapping: Configuration table that enables you to create mappings between ServiceNow CMDB configuration items and Dynatrace monitored entities. Once mapping has been configured, incoming problems are automatically attached to the affected configuration item.

Configuration within ServiceNow

To complete configuration on the ServiceNow side, copy and paste your Dynatrace environment ID and API key into the Dynatrace environments table within ServiceNow, as shown below. Your Dynatrace environment ID is the first part of your Dynatrace environment URL (i.e., <EnvironmentID>

To create an API key for your Dynatrace environment

  1. Navigate to Dynatrace > Settings > Integration > Dynatrace API.
  2. Click the Generate token button.

If you're running a Dynatrace Managed instance, the server runs within your own datacenter. Therefore, a Cluster Gateway with a publicly accessible domain is necessary. For Dynatrace Managed installations the URL pattern looks like the following example:


Configuration within Dynatrace

After installing and configuring Dynatrace integration on the ServiceNow side, switch over to your Dynatrace environment.

Navigate to Dynatrace > Settings > Integration > Problem notifications, click Set up notifications, and select ServiceNow, as shown below.

On the Set up ServiceNow integration page, type a custom name for your new integration (for example, My new ServiceNow Integration). Enter your ServiceNow instance identifier as shown above (for example, dev23082) and enter a ServiceNow user name that has the following roles assigned to it:

  • x_dynat_ruxit.Integration
  • rest_service
  • web_service_admin

If you're running a ServiceNow instance within your own domain, use the domain of your instance instead of the instance identifier.

Problem-description placeholders

You can customize the short description texts of the problem-notifications that are sent out by defining a text template that includes placeholders that are dynamically populated with relevant problem details, such as problem ID, problem impact, or problem state. By default, the full HTML formatted description of each detected problem and a direct link to the corresponding Problem details page in Dynatrace is attached to each ServiceNow incident in the form of a comment.

  • {State}: Problem state. Possible values are OPEN and RESOLVED.
  • {ProblemID}: ID number of the reported problem.
  • {PID}: A unique system identifier for the reported problem.
  • {ProblemImpact}: Impact level of the problem. Possible values are APPLICATION, SERVICE, and INFRASTRUCTURE.
  • {ProblemTitle}: A short description of the problem.
  • {ImpactedEntity}: Entities impacted by the problem (or the term "multiple" when more than two entities are impacted).
  • {Tags}: Comma-separated list of tags that that have been defined for all impacted entities.

Push incidents and/or ITOM events

By using the toggles for sending incidents and/or ITOM events, you can control when Dynatrace should automatically create an incident within the ServiceNow ITSM module and if all individual correlated events should be pushed into the ServiceNow ITOM events API.

Automatic incident creation

Once configuration is complete on both the Dynatrace and ServiceNow sides, problem notifications are pushed from Dynatrace to your ServiceNow instance, as shown below:

Dynatrace as ITOM event source

In the case that the ITOM module is enabled within your ServiceNow instance, Dynatrace can also act as an ITOM event source. Once you've enabled the push of ITOM events on the configuration page, all correlated events that were detected by Dynatrace are automatically pushed into the ITOM event API. Each host-based event has the correct node name and node IP attached as well as important severity information within the additional information field. ServiceNow ITOM users can create event filters and alerting rules to flexibly react to incoming Dynatrace-detected events. Each of the events contains the unique Dynatrace identifier (for example, HOST-B66B773D12C49189) within the field correlation_id. In case the default ITOM CI mapping isn't able to match a CI by its node name, this correlation_id is used to automatically map detected CIs. An example of such a process event is shown below:

By configuring Dynatrace as an ITOM event source, you can further improve real-time visibility into your complete IT technology stack.

Your ServiceNow ITOM dashboard will immediately visualize the health state of all your business services, as shown below:

Manual CMDB mapping of detected problems

Dynatrace automatically detects problems within your environment, correlates all related events and affected components that share the same root cause, and presents all problem-analysis data so that they can easily be tracked and analyzed. When Dynatrace pushes a problem to your ServiceNow instance, it may contain multiple affected configuration items.

The CI Mappings table, which is found in the ServiceNow Dynatrace menu, can be used in cases where automatic mapping of your CMDB configuration items with incoming problems is necessary. The CI Mappings table represents a lookup table where Dynatrace component IDs are mapped with your CMDB CIs. If there is a valid mapping between an incoming affected component, and an existing CMDB CI is present, the ServiceNow Dynatrace application attaches the affected CMDB CI to the created incident.

The image below shows you how to map CIs to Dynatrace IDs:

Frequently asked questions

Why are Dynatrace detected hosts, process groups, and services not shown within the CMDB? To allow Dynatrace to report discovered CIs into your CMDB you must create a new discovery data source called DYNATRACE. Please follow the instructions below:

  1. Navigate to System Definition > Choice Lists.
  2. Click the New button.
  3. Create a new entry with following detail: Table: Configuration Item [cmdb_ci] Element: discovery_source Label: DYNATRACE Value: DYNATRACE

Which ServiceNow tables are filled by the ServiceNow Dynatrace application?

Dynatrace sends all detected problems into the ServiceNow incident table (incident). All single events that are correlated with a Dynatrace-detected problem are sent to the ITOM event table (em_event). The relationship between a CI and a Dynatrace-detected problem is sent into the CIs Affected table (task_ci). If enabled, Dynatrace synchronizes all auto-discovered web applications and web services into the CMDB business services table (cmdb_ci_service). All hosts and process groups running on those hosts are synchronized into the CMDB server table (cmdb_ci_server) and CMDB cluster table (cmdb_ci_cluster).

Which scheduled jobs are introduced to pull the CMDB information from Dynatrace?

Dynatrace introduces one scheduled job that pulls a subset of the topology information from Dynatrace Smartscape at 10-minute intervals. The scheduled job Dynatrace sync CMDB job pulls all web application information, along with their relation to software services, all host and process group information, and all software services and relationships. The information pull is performed using the official Dynatrace REST API.

Can I change the table or field to where Dynatrace pushes the data?

Incidents are imported through an import set table. You can reconfigure the default transformation map Problem to Incident Transformation Map to route the information to different tables or fields.

Can I synchronize additional information, or even metrics?

The Dynatrace ServiceNow application is built entirely on the public Dynatrace API and it uses a subset of this information by default. The best approach here is to use the ServiceNow Dynatrace application as a starting point and to customize information retrieval based on your requirements. It’s even possible to fetch detailed real-time metrics for each of your Dynatrace monitored configuration items using the Dynatrace API.

Does Dynatrace automatically merge existing CIs with Dynatrace discovered CIs?

Deduplication is done through ServiceNow CMDB Identification and Reconciliation. Custom CI identification rules are used to merge identical CIs based on a given attribute (for example, IP address).

Does Dynatrace integration support multiple environments?

Yes, multiple Dynatrace environments can be configured within the Dynatrace environments table in ServiceNow.

Why are Dynatrace detected services not shown within the business services table?

You must create a CI identification rule for Dynatrace detected services.

  1. Navigate to Configuration > Identification/Reconciliation > CI Identifiers.
  2. Click the New button.
  3. Type Applies to: cmdb_ci_service.
  4. Add an identifier entry (as shown below) that contains the criteria name and correlation_id.

How do I fix an HTTP 403 Forbidden Access Restricted Not Authorized Error when sending a test notification?
If you receive a UI error when running a test notification for ServiceNow that says HTTP Status 403 - Access restricted ([IP Address] not authorized), you'll need to add the IP Address listed in the error to your ServiceNow whitelist. For information about whitelisting IPs in ServiceNow, please refer to ServiceNow documentation.

How do I fix an HTTP 403 Forbidden User Not Authorized Failed API Level ACL Validation error when sending events into ServiceNow ITOM?
If you run into this error when configuring the toggle to Send Events into ServiceNow ITOM, ensure that your ServiceNow instance's ITOM is enabled. By default, development instances of ServiceNow have ITOM disabled, making it impossible for Dynatrace to successfully send event data into your ServiceNow environment. For instructions on how to enable ITOM, please see ServiceNow Documentation.