Propagating the NAM Probe configuration

To copy configurations to NAM Probes, in addition to using the NAM Console, you can also use automatic propagation through the NAM Console.

A full NAM Probe configuration exports into five XML files:

  • applications.xml for global settings and services
  • avagt.xml for Dynatrace Network Analyzer agent settings.
  • nfc.xml for Flow Collector settings.
  • page2trans.xml for transaction definitions
  • protocols.xml for predefined software services The computer hosting the NAM Console maintains a copy of the current configuration for each of the NAM Probe devices in the *<installation directory>* \cva\eclipse\workspace\configuration\amd\export folder. The NAM Console automatically generates four XML configuration files per NAM Probe in the NAM Console devices list.

The name of each of the exported XML files contains the IP address and port number of the associated NAM Probe. These files are located on the NAM Console in the folder *<installation directory>* \cva\eclipse\workspace\configuration\amd\export .

Modify these files then propagate the configuration to several or all of the NAM Probes in the NAM Console Devices list.

A configuration file must have one of four standard names (applications.xml, avagt.xml, page2trans.xml, or protocols.xml) and may be further qualified with an IP address and port number.


  • Suppose the \import folder contained XML files named as follows:

    • applications.xml
    • avagt.xml
    • nfc.xml
    • page2trans.xml
    • protocols.xml

    In this case, the NAM Console applies these configuration files to all NAM Probes available in the NAM Console Devices list, regardless of IP address.

  • Suppose the \import folder contained the following set of XML files:


    Note that the file names now contain an IP address and port number. In this example, the NAM Console automatically applies each of these configuration files only to the NAM Probe with IP address using port number 9091. Any other NAM Probes are not affected.

  • Suppose the \import folder contained just a subset of those files:


    In this example, the NAM Console applies the listed XML configuration files to that NAM Probe. Because the other configuration files are not available, the parts of the configuration affected by the missing configuration files remain unchanged on that machine.

  • Suppose the \import folder contained two of the same type of XML file, one with a specific IP address and the other without:

    • applications.xml

    In this case, the NAM Console applies the applications.xml configuration file to all NAM Probes except the NAM Probe at address, which receives the contents of instead. An address-specific configuration file always overrides a general configuration file of the same type.

  • Suppose the \import folder contained XML files whose names did not adhere to the above file naming syntax, such as:

    • my_configuration_applications.xml
    • some-file_avagt.xml
    • test-amd-page2trans.xml
    • all_protocols.xml

    In this case, the NAM Console ignores these files and would not propagate any settings they might contain.

To propagate a configuration set from one NAM Probe to the rest of the NAM Probes, copy the XML configuration file set from the ..\CVAConfig\amd\export folder to the ..\CVAConfig\amd\import folder and rename all four file names so they do not include the IP address and port number. The NAM Console will publish the configuration within 60 seconds of a change detection. Considering that a default directory check occurs every 60 seconds and by default the publish delay is set to 60 seconds, the maximum wait for the configuration to begin propagating is 120 seconds after a new configuration file has been added to the ..\CVAConfig\amd\import folder.

Copying the NAM Probe configuration using NAM Console

After a NAM Probe has been added to Devices, the NAM Console can distribute that configuration to other devices of the same type.

To propagate the NAM Probe configuration to one or more other NAM Probes:

  1. In NAM Console ► Deployment ► Manage devices.

  2. In NAM Console ► Deployment ► Manage devices, find the source NAM Probe, open the menu for it, and select Current configuration ► Copy.
    Optionally, you can propagate an unpublished configuration by selecting the Draft configuration ► Copy from the context menu for a given NAM Probe. Note that propagating a draft configuration will overwrite the draft configurations on all of the destination NAM Probes.

  3. In the pop-up window, select the NAM Probes to which you want to copy the configuration (the destination NAM Probes).
    To ensure configuration compatibility, verify that all NAM Probes involved are of the same version.

  4. Specify whether to propagate the entire configuration or whether to propagate selected parts of the configuration.

    • To propagate the entire configuration, select Whole configuration.
    • To propagate only specific parts of the configuration, select Part(s) of configuration and then select the configuration components to propagate.
  5. Click OK.


    After you add a NAM Probe as a device, if its configuration is older than the RUM Configuration's, the current NAM Probe configuration for global settings and services (applications.xml) and pre-defined software services (protocols.xml) will be upgraded automatically. The configurations for all NAM Probes connected as devices are also updated after each NAM Console upgrade.

After the configuration is propagated to the selected destination NAM Probes, a message appears indicating that the draft configuration has been updated.

What to do next

The distributed configuration is presented as an updated draft for each of the destination NAM Probes. You must still publish all of the drafts before the new configuration takes effect. You can publish draft configurations individually for each NAM Probe or click Publish Configuration on the Devices screen to publish them all at once.