Why are there no connection metrics for a tier, node, or network link?

By default, Network Agents do not collect connection metrics. The recommended workflow is to identify the link with the network issue and configure the relevant agents to collect metrics for the relevant connections. See Dynamic Monitoring Mode and Network Visibility.

The Network Agent cannot register with the Controller. What should I do?

If a Network Agent cannot register with the Controller:

• Check that the user account has a Network Visibility product license.
• If the user account has license rules defined, verify that the correct number of license units have been allocated.
• To change the number of allocated units in a rule:
  • Go to Controller Settings > License > Rules.
  • Edit the License Rule of interest. (There may be only one License Rule, named Default.)
  • In General, set the Allocated Units field for the Network Visibility license and apply the change.

In some cases, I see that an application flow for a JMS queue goes in one direction but a TCP connection used by that queue goes in the opposite direction. Why is that?

Typically, the network links and TCP connections used by an application flow have the same direction (source → destination) as the flow itself. You may notice different directions, however, if two tiers transfer data through a JMS queue. In some JMS implementations, the individual nodes in each tier initiate the TCP connection to the queue, so the direction is always: node (source) → queue (destination).

Some of these connections may be used by an application flow in the opposite direction: queue (source) → tier (destination).

How do I change the Network Agent communications port?

When you start the Network Agent, the appd_netmon appd-agent

1. Use the netstat command to verify that the new port is not in use.
2. Update the Network Agent:
   1. Use a text editor to open this file: <network_agent_home>/conf/agent_config.lua .

   2. Set the port webserver_config

      webserver_config = {
      port = <new-port-number>,
      request_timeout = 10000,
      threads = 2,
      }

   3. Save the file and restart the Network Agent.
3. Update the App Agent:
   1. Use a text editor to open this file: <app_agent_home>/<version-number>/external-services/netviz/netviz-service.properties .
   2. Set the netviz.agent.api.service.port option to the new TCP port number.
   3. Save the file and restart the App Agent.

The application I want to monitor uses TCP port 32768 or higher. How do I configure the Network Agent to monitor this port?

1. Use a text editor to open this file: <

2. If you plan to monitor any application or service that uses any TCP ports higher than 32767, uncomment the application_service_ports ports

   Original:

   --[[ application_service_ports = { ports = "", } --]]

   Edited:

   application_service_ports = { ports = "40000, 41000", }

How can I replace the AppDynamicsNetMQ.dll with another version of NetMQ?

1. Download the NetMQ.dll version and its dependencies.
2. ILMerge them into one dll file named AppDynamicsNetMQ.dll .
3. Include the AppDynamicsNETMQ.dll file in the .NET Agent home directory, such as c :\Program Files\AppDynamics\AppDynamics .NET Agent .
4. Restart the monitored application.

Are there any additional fully qualified domain name (FQDN) configurations for the agent_config.lua file?

ip_config = {
expire_interval = 20,
retry_count = 5,
}

Refresh Timeout: expire_interval

Retry Count: retry_count expire_interval