AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.


    Skip to end of metadata
    Go to start of metadata

    Related pages:

    Your Rating:
    Results:
    1 Star2 Star3 Star4 Star5 Star
    32 rates

    Before you enable Network Visibility, you should review these guidelines. 

    System Requirements

    Network Visibility requires a supported version of the Network Agent to be installed on the monitored server. 

    Network Visibility features are available for Linux and Windows. You need a Network Visibility license to enable and use Network Visibility features. Network Visibility is enabled by default on AppDynamics Controllers. See License Entitlements and Restrictions

    Linux System Requirements

    Network Visibility requires:

    • Controller version 4.4 or higher with a Network Visibility license.
    • You must have sudo or root access permissions on the Agent host to install the Network Agent. You do not need sudo or root access to run the Agent.
    • Each host on Linux must have:
      • Network Visibility Agent (version 4.4 or higher)
      • Java App Server Agent (version 4.4 or higher) with an App Agent license
    • Network Visibility is supported on Linux hosts with Java App Server Agents only.

    Network Visibility on Linux

    The Network Agent is supported on Linux distributions based on glibc 2.12 or higher:

    • CentOS 6 and higher (32-bit and 64-bit)
    • Ubuntu 14 and higher (32-bit and 64-bit)
    • Red Hat Enterprise Linux 6 and higher (32-bit and 64-bit)
    • Fedora 24 and higher (32-bit and 64-bit)

    The Network Agent host must have these libraries pre-installed:

    • libdl.so.2
    • libpthread.so.0
    • librt.so.1
    • libm.so.6
    • libc.so.6
    • libncurses.so.5
    • libtinfo.so.5
    • libstdc++.so.6
    • libgcc_s.so.1

    Windows System Requirements

     Each Windows host must have:

    Network Visibility on Windows

    The Network Agent is supported for Java applications on these Windows distributions:

    • Windows Server 2019 (64-bit)
    • Windows Server 2016 (64-bit)
    • Windows Server 2012 (64-bit)
    • Windows Server 2012 R2 (64-bit)
    • Windows Server 2008 (64-bit)
    • Windows Server 2008 R2 (64-bit)

    The Network Agent is supported for .NET applications running on Windows starting with .NET Framework version 3.5 on these runtime environments: 

    • 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 .NET Agent if you have installed:

    • Network Agent version 4.5.7 or higher
    • .NET Agent version 4.5.15 or higher
    • AppDynamics Controller version 4.5.14 or higher

    You can monitor .NET applications that are implemented using synchronous calls. However, Directory Search and ADO.NET are not supported.

    Network Visibility is not enabled by default. You can enable it by setting the Agent node property socket-enabled=true. See App Agent Node Properties (S)

    Support for monitoring network traffic for asynchronous .NET calls is limited. If your asynchronous .NET calls are not reporting network traffic correctly, contact Support to report your use case, including libraries/api/framework involved in the transaction. This information will be passed on to the Product team for possible enhancements.

    Limitations

    • This release does not support these Network Flow Map features:
    • Federated Flow Maps
    • Visualization of flows between web servers and APM entry tiers
    • The Network Flow Map does not filter out connections based on the selected time range
    • 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. 

    • You cannot view Health Rule violations in the Network Dashboard. To view any Health Rule violations, including those based on Network Visibility data, access the Application Dashboard. 

    Known Issues

    • If you open the Network Flow Map for an individual node, the KPI metrics for node-to-load-balancer and 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. 
    • Network Visibility cannot monitor Cross Application Flows that use Jersey web servlets. As a workaround, you can disable Jersey servlet instrumentation. This causes Business Transactions on these flows to become recognized as servlets instead of Web Services. To implement this workaround:

      1. Select the application of interest in the Controller UI.
      2. Select Configuration > Instrumentation > Transaction Detection.
      3. Disable instrumentation for Jersey Servlet and Jersey 2.x Servlet.
      See Network Visibility Known Issues in the Release Notes


    • No labels