Unifying DC RUM data with Dynatrace SaaS and managed

DC RUM and SaaS/Managed unification gives you a complete insight into your application performance.

  • If you already have DC RUM, by adopting Dynatrace SaaS/Managed you get deep visibility into critical process and OS-related metrics on servers monitored with DC RUM - all in the new Dynatrace user interface where all DC RUM and agent-based measurements come together.
  • If you are laying out complete new Dynatrace setup, DC RUM will complement your visibility into performance of the critical apps of record, like SAP, Citrix, SSL-delivered apps and those web apps which are not instrumented with UEM yet.

How DC RUM and Dynatrace SaaS/Managed unification works

The AMD monitors the OneAgent instrumented servers. Both AMD and OneAgent identify the server with the same IP addresses and port. The DC RUM CAS sends the preprocessed monitoring data to the Dynatrace cluster or tenant, where we match and report the data at the process level.

What do I need to start the unification?

  • You have already created software services for your Web, SAP or Citrix applications in DC RUM.

  • You have enabled the CAS connectivity to Dynatrace SaaS/Managed instance. The CAS should be able to connect to a managed cluster or SaaS tenant URL on port 443.

  • To get the most of the unification, you should deploy OneAgent on each host on which you based your DC RUM software services. You can do it when the unification is up and running - Dynatrace SaaS/Managed discovers the candidates and guides you in OneAgent deployment. See How do I install Dynatrace OneAgent.

  • You must be able to sign in as an administrator to both RUM Console and Dynatrace SaaS/Managed.

  • Make sure you use a right browser. Any of the DC RUM supported browsers lets you access both DC RUM and Dynatrace SaaS/Managed.

How do I enable the unification?

The core configuration is straightforward. In short, first add the Dynatrace Managed cluster or SaaS tenant as a new device in RUM Console and then assign it as a data stream to CAS. After you save the configuration, the CAS starts sending the monitoring data to Dynatrace right away.

Add Dynatrace Managed cluster or SaaS tenant to RUM Console. 
In RUM Console, add Dynatrace as one of the devices, see Add device. You need to provide the URL and Dynatrace authentication token to authorize the connection between CAS and Dynatrace. You can copy/paste a token or import one automatically. In both cases, you need to be able to sign in as Dynatrace SaaS/Managed administrator.
Get token on the Dynatrace side (Settings > Integration > Dynatrace modules) and paste it in the RUM Console when adding the Dynatrace SaaS/Managed device type in the Add device dialog.

Assign the device you just added as the CAS data stream. See Data sources and destinations

Configure the CAS data export.
In the RUM Console, go to CAS configuration and click DC RUM SaaS/Managed data export. Here you can select the scope of the exported data. You can either export all data or limit the type of data that are exported by selecting one of three options:

  • Data from user-defined software services (i.e., no auto-discovered services)
  • Data from selected software services
  • Data from specific analyzer groups

Note: If you select Export all, the CAS will only send the data gathered by the analyzers that are supported by the integration (i.e., web, SAP, SAP RFC, or Citrix). Click the Apply button to save your changes.

DC RUM lets you further analyze your data center issues by providing context drilldown links to DC RUM CAS. By default, the link is built based on the CAS IP address or hostname used by RUM Console for the device management. If it's an internal address, accessible only from within your private network, you may want to replace it with a public CAS URL for the DC RUM users outside your network. Expand the Advanced configuration section and add the public CAS URL as the Drilldown URL. You can also add a URL pointing to your CAS failover server, if you've set one up.

Where can I see the DC RUM data in Dynatrace?

If you're familiar with DC RUM, the good point to start is to follow a link to Dynatrace SaaS/Managed from the Software Service  column in the Operation explorer report.

Clicking it, you land right on the data service screen. Note that the link is available only for the services that are exported to Dynatrace SaaS/Managed.

This is what happens with the DC RUM data once Dynatrace SaaS Managed processes it:


We use the HTTP decode not only to analyze the web apps, but also SOAP, XML and Oracle Forms enterprise applications. For the HTTP based software services, the unification works for both, user-defined and autodiscovered software services. For each autodiscovered software service exported to Dynatrace, we simply report a corresponding data center service. For user-defined software services, we will additionally report the application, if you already deployed OneAgent on a host defined in the software service configuration, or a candidate, if you did not.


We report on two flavors of SAP. SAP GUI, a UI frontend for SAP applications and SAP RFC, the application backend.

For each exported SAP GUI user-defined software service, we report a corresponding data center service and application/candidate per each SAP SID.

For each exported SAP RFC user-defined software service, we report a corresponding data center service only.


For each exported Citrix user-defined software service, we always report both, a corresponding data center service and an application/candidate.


You can find all the entities related to your monitored environment, that is services, applications, processes and hosts on the smartscape. Using it, you can analyze the relations between one another, discover hosts where you can deploy OneAgent or identify applications and services you might have not been aware of. Browsing through the smartscape, you can drill down to screens with the detailed reports on the performance of each entity.

Applications/data center services

For both, Enterprise applications and data center services, you gain access to both DC RUM metrics and OneAgent collected events indicating the OS related problems that may affect the performance of your application.

For automatically detected web sites, served by the web servers such as Tomcat or Apache, you gain access to Dynatrace application performance analysis.


For each host on which you deploy Dynatrace OneAgent, you gain insight into host performance measures with the access to the log analytics.

Are there any known limitations of the unification?

This is a first stage in the development of the unification and there are some snags we would like to improve in future releases:

  • There's no Single Sign-on between DC RUM and Dynatrace available just yet
  • You can send data from a number of CASes to one tenant or cluster. If this is your case, make sure these CASes do not overlap in their services reporting, because the Dynatrace SaaS/Managed does not have any means to deduplicate the data.
  • Dynatrace SaaS/Managed will report only user aggregates. There's no visibility into real users' actions and experienced performance just yet.
  • Although it's technically possible to export data from from one CAS to many Dynatrace SaaS/Managed instances, we recommend adding just one data destination to the CAS.

See also: DC RUM - Dynatrace SaaS and Managed Unification Q&A