This page describes application environments, operating systems, and version support for the Network Agent.
With a Network Visibility license, you can use Network Visibility features on Linux and Windows. You must have a supported version of the Network Agent to be installed on the monitored server. See License Entitlements and Restrictions.
By default, Network Visibility is disabled in the Controller. To enable Network Visibility, set the agent node property
socket-enabled=true. See App Agent Node Properties (S).
Network Visibility is not supported on JDK 1.6. To run the Network Agent, upgrade to JDK >= 1.8.
Network Visibility is compatible with Kubernetes and Docker, but not Docker Swarm.
Network Visibility on Linux
Operating System Requirements
Network Visibility is supported on Linux hosts with Java app server agents only.
Each host on Linux must have:
- Network Visibility Agent >= 4.4
- Java Agent >= 4.4 with an App Agent license
- Controller >= 4.4 with a Network Visibility license
You must have
root access permissions on the Agent host to install the Network Agent. You do not need
root access to run the agent.
The following Linux distributions support the Network Agent based on glibc >= 2.12:
- CentOS >= 6 (32-bit and 64-bit)
- Ubuntu >= 14 (32-bit and 64-bit)
- Red Hat Enterprise Linux >= 6 (32-bit and 64-bit)
- Fedora >= 24 (32-bit and 64-bit)
You must install these required libraries before installing the Network Agent host:
Network Visibility on Windows
Operating System Requirements
Each Windows host must have:
- Network Visibility Agent >= 4.5.7.
- An account with administrative privileges on the Windows machine where you want to install the Network Agent.
Additionally, each Windows host must also have:
- .NET Agent >= 4.5.15 with an App Agent License. See Install the .NET Agent and Observe License Usage.
- Controller >= 4.5.14 compatible with the .NET Agent.
- Java Agent >= 126.96.36.19986 with an App Agent license. See Install the Java Agent and Observe License Usage.
Controller >= 188.8.131.5286 compatible with the Java Agent. See Agent and Controller Compatibility.
To install AppDynamics for testing, you need to verify system requirements, prepare the host, and perform the Controller installation. See Upgrade the Controller Using the Enterprise Console and Install the Controller Using the CLI.
The following Windows distributions support the Network Agent on Java applications:
- Windows Server 2019 (64-bit)
- Windows Server 2016 (64-bit)
- Windows Server 2012 (64-bit)
- Windows Server 2012 R2 (64-bit)
The following Windows runtime environments support the Network Agent on .NET applications (starting with .NET Framework version 3.5):
- Microsoft IIS versions 6.0, 7.0, 7.5, 8.0, 8.5, 10
- Managed Windows Services
- Managed Standalone Applications
You can use the Network Visibility features with the .NET Agent if you have installed:
- Network Agent >= 4.5.7
- .NET Agent >= 4.5.15
- AppDynamics Controller>= 4.5.14
Network Visibility is not supported for .NET core based applications. Ensure to set
socket-enabled node property to
false to such nodes.
You can monitor .NET applications that are implemented using synchronous calls. However, Directory Search and ADO.NET are not supported.
AppDynamics does not currently support monitoring network traffic for asynchronous .NET calls.
The following Network Flow Map features are not supported:
- Federated Flow Maps
- Visualization of flows between web servers and APM entry tiers
The Network Flow Map does not filter out connections on the selected time range.
Cross-application correlation of a .NET application with Network Visibility is not supported for .NET environments.
The Network Agent cannot monitor multiple app server agents on the same host if these agents report to different Controllers. All app server agents must report to the same Controller.
The Network Dashboard does not show data for Health Rules or Health Rule violations. To view any Health Rule violations, including those based on Network Visibility data, access the Application Dashboard.
Network Visibility cannot monitor cross-application flows that use Jersey web servlets. As a workaround, disable Jersey servlet instrumentation and business transactions on the flows will be recognized as servlets instead of web services:
- Select the application of interest in the Controller UI.
- Select Configuration > Instrumentation > Transaction Detection.
- Disable instrumentation for Jersey Servlet and Jersey 2.x Servlet.
If you open the Network Flow Map for an individual node, the KPI metrics for
node-to-TCP-endpoint links show network KPIs for all nodes in the parent tier (instead of KPIs for the individual node only). To view KPIs for the individual node, open the link popup and review the Connection KPIs.