Time to upgrade! NAM is scheduled for end of support. It's time to move to Dynatrace our all-in-one software intelligence platform.

Unifying NAM data with Dynatrace SaaS and Managed

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

  • If you already have NAM, by adopting Dynatrace SaaS/Managed you get deep visibility into critical process and OS-related metrics on servers monitored with NAM - all in the new Dynatrace user interface where all NAM and agent-based measurements come together.
  • If you are laying out a complete new Dynatrace setup, NAM 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 NAM and Dynatrace SaaS/Managed unification works

The NAM Probe monitors the OneAgent instrumented servers. Both NAM Probe and OneAgent identify the server with the same IP addresses and port. The NAM Server 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?

  • All software services monitored by NAM can now be integrated with Dynatrace Managed (or Dynatrace SaaS), delivering a single landing spot for all monitored applications and infrastructure.

  • You have enabled the NAM Server connectivity to Dynatrace SaaS/Managed instance. The NAM Server 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 NAM 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 NAM Console and Dynatrace SaaS/Managed.

  • Use a supported browser. Any of the NAM supported browsers lets you access both NAM 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 NAM Console and then assign it as a data stream to NAM Server. After you save the configuration, the NAM Server starts sending the monitoring data to Dynatrace right away.

Add Dynatrace Managed cluster or SaaS tenant to NAM Console.

  1. In the NAM 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 the NAM Server and Dynatrace. You can copy and paste a token or import one automatically. In both cases, you need to be able to sign in as Dynatrace SaaS/Managed administrator.
  2. Get a token on the Dynatrace side (Settings > Integration > Dynatrace modules) and paste it in the NAM Console when adding the Dynatrace SaaS/Managed device type in the Add device dialog.

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

Configure NAM Server data export.

  1. In the NAM Console, open the Devices screen (Deployment ► Manage devices).
  2. Find the NAM Server in the list of devices and select Open configuration for that NAM Server.
  3. On the NAM Server configuration screen, click NAM 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

Click the Apply button to save your changes.

NAM lets you further analyze your data center issues by providing context drilldown links to the NAM Server. By default, the link is built based on the NAM Server IP address or hostname used by NAM 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 NAM Server URL for the NAM users outside your network. Expand the Advanced configuration section of the screen and add the public NAM Server URL as the Drilldown URL. You can also add a URL pointing to your NAM Server failover server if you've set one up.

Where can I see the NAM data in Dynatrace?

If you're familiar with NAM, a good point to start is to follow the Further analyze on Dynatrace dashboard link from the Software Service column in the Operation explorer report.

That lands you 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 NAM data once Dynatrace SaaS Managed processes it:

NAM 2019

In NAM 2019, we've enhanced application mapping for NAM unification with Dynatrace SaaS and Managed. Now you can also use NAM application names as defined using Business units (on the NAM Server navigation menu, select APM model ► Business units) or disable automatic creation of Enterprise Applications in Dynatrace.

Edit <install_dir>\config\platform-export.yaml and paste one of the three options below. You don't need to restart the NAM server.

  • Default
    The Dynatrace Enterprise Application names are mapped to NAM entities according to the algorithm used in NAM 2018. See information below for reference.

    # platform  
    - Dynatrace SaaS-Managed export  
  • Do not export applications at all
    No NAM applications are exported to Dynatrace.

    # platform  
    - Dynatrace SaaS-Managed export no applications  
  • Export applications based on NAM applications defined in Business units
    Only NAM applications defined using business units configuration are exported to Dynatrace and presented as Enterprise Applications.

    # platform  
    - Dynatrace SaaS-Managed export bu applications  

What NAM entities are forwarded to Dynatrace

NAM Analyzer NAM technical hierarchy In Dynatrace visible as Remarks
Software service Data center service
Server IP address IP addresses
Server port list Ports
SAP GUI SAP GUI over HTTP SAP RFC Service (=SID for SAP GUI) Application (type = enterprise)
HTTP HTTP Express URL host (=http hostname) Or Task (=1st host name in SSL cert when URL host is -) Application (type = enterprise)
SSL Task (=1st host name in cert) Application (type = enterprise) Only SSL handshake operations are measured for response time
Citrix Server IP address Application (type = enterprise)
  • All other analyzers 
    See Dynatrace SaaS-Managed export  DMI report on your CAS for more details.


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. For each exported SAP GUI user-defined software service, we report a corresponding data center service and application/candidate per each SAP SID.
  • SAP RFC: the application backend. 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 a corresponding data center service and an application/candidate.


You can find all the entities related to your monitored environment: 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 Enterprise applications and data center services, you gain access to both NAM 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 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 NAM and Dynatrace available just yet.
  • You can send data from a number of NAM Servers to one tenant or cluster. If this is your situation, make sure these NAM Servers 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 one NAM Server to many Dynatrace SaaS/Managed instances, we recommend adding just one data destination to the NAM Server.

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