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

Configuration overview for NAM Probe network performance monitoring

Before you begin

  • Be familiar with NAM components and basic monitoring concepts.
  • Install the following NAM components:

Follow these steps to set up network performance monitoring using NAM Probes as primary network probes and NAM Server as the reporting engine.

Defining data sources and servers

Add NAM Probe

The NAM Probe is the main data source (Data Collector) for NAM; it collects and presents the monitored data to NAM report servers for analysis and reporting. You need to add at least one NAM Probe to the list of devices in the NAM Console.

Add NAM Server

The NAM Server is the main report server for NAM. It uses data provided by the NAM Probe and its monitoring and alerting mechanisms to identify, track, and report on issues affecting the security, performance, and reliability of your services. Add at least one NAM Server to the device list and configure its connection with the NAM Probe. Adding a report server to a list of devices is similar to adding the NAM Probe.

Verify the traffic monitoring quality and completeness

You can verify traffic quality and completeness before the actual monitoring begins. Sniffing point diagnostics allows you to perform pre-monitoring tasks without the need of accessing the NAM Probe console and executing a series of Linux commands which usually serve the purpose of validating NAM Probe physical installation and connection.

Deciding on NetFlow vs datacenter analysis and configuring NetFlow-enabled devices

Deciding on NetFlow vs datacenter analysis

Decisions taken at this point will affect the configuration steps performed later.

Network performance monitoring can be based on NetFlow analysis as well as on passive analysis of network traffic on selected data center devices. You can use both of these types of analysis to satisfy your requirements. Options available to you depend on the product license you have purchased. For more information, see Deciding on NetFlow vs. Traffic Monitoring Analysis.

Optional: Configuring NetFlow-enabled devices to deliver NetFlows to the NAM Probe.

If NetFlow analysis is required, the specific routers and other NetFlow-enabled devices have to be configured to send NetFlows to the NAM Probe. Refer to appropriate documentation of your NetFlow-enabled devices for instructions on how to perform the configuration. For more information, see Configuring remote NetFlow-enabled devices.

Configuring NAM Probe

Specifying basic NAM Probe settings.

Before you proceed to detailed monitoring rules, you need to define global settings that will be applied to all the monitoring and analysis performed on a given NAM Probe. These global settings include:

The monitoring interval

You are unlikely to need to modify this setting for the purpose of network analysis, but you can adjust it if you need a different granularity of results.

Operation time threshold

This setting will affect one of the protocol analyzers used for network performance monitoring: “Generic (with transactions)”. This setting can be overridden by settings for specific software services you define later, based on this analyzer.

Optional: Configuring general NetFlow settings on the NAM Probe

For more information, see Flow collector - general.

Optional: Fine-tuning flow sources

After you have configured flow-enabled devices to send flows to the NAM Probe, the observed devices will start appearing in the NAM Probe Flow Sources table. You may then need to adjust the settings for individual devices. For more information, see Flow collector - flow sources.

Optional: Viewing NetFlow reports on the report server and re-adjusting monitoring configuration settings

After viewing network reports on the report server, you may need to modify NetFlow monitoring settings to better suit your purposes, remove or add more flow sources, or modify flow analysis settings.

An extensive set of network performance monitoring reports has been provided. You can also design your own reports or customize some of the reports that have been provided. For more information, see Network Analysis.

Optional: Deciding on traffic monitoring analyzers and configuring global monitoring setting for these analyzers.

Select one or more traffic monitoring analyzers to be used for network performance monitoring, and define global settings for these analyzers if any are available. These are settings that affect monitoring of all services based on the given analyzer. For network performance monitoring, you are advised to select those analyzers that provide network-related information without in-depth transactional or payload analysis. The recommended analyzers and their global settings are:


This analyzer provides only basic measurements (no realized bandwidth and transaction monitoring). There are no global settings specific to this analyzer.


This protocol provides basic measurements and realized bandwidth. There are no global settings specific to this analyzer.

Generic (with transactions)

This protocol provides basic measurements, realized bandwidth and transaction metrics. There are no global settings specific to this analyzer except the transaction threshold as set for all analyzers supporting transactions. For more information, see Specifying basic NAM Probe settings.

HTTP Express

Use this analyzer if it is known that HTTP traffic is present and you require basic HTTP information about servers and URLs. This analyzer has a number of general options for all the services based on it.

Optional: Defining custom software services for passive traffic monitoring

Define custom software services for the selected analyzers. For more information, see Software Services.

There are additional specific settings for the HTTP Express analyzer that should also be configured for software services based on that analyzer.

Fine-tuning and troubleshooting

Viewing reports and fine-tuning configuration.

Determining the best possible configuration for your needs may be an iterative process, where you will fine-tune the configuration incrementally after viewing your report results. For more information, see Network Analysis.

Troubleshoot problems

You can review the answers to the most common questions and troubleshoot your setup and report configurations.