On this page:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
6 rates
The following notes describe 4.5.x updates to Network Visibility.

If an artifact has been updated, the version number of the updated artifact and its availability date are listed below. The version number corresponds to that shown on the download portal (http://download.appdynamics.com).

The most recent releases appear at the top of the page.

4.5.8 Updates

Network Agent

Version 4.5.8.1960 – July 23, 2019

Enhancements

The REST APIs for Network Agent version 4.5.7 or earlier are bound to all available network interfaces. With agent version 4.5.8, the REST APIs are by default bound to the localhost only. You can change this configuration using 'webservice_ip' parameter in the agent_config.lua file. This affects the docker and Kubernetes deployment of the Network Agent. For more information, see:

Resolved Issues

 

Key
Summary

NETWORK-5430

JVMs in WebSphere take longer time to shut down when JAVA webservers are configured with LD_PRELOAD option

NETWORK-5196

Network Agent consumes high memory when DNS resolutions fail

 

4.5.7 Updates

Network Agent

Version 4.5.7.1933 – June 27, 2019

Enhancements
  • Network Agent version 4.5.7 and Java Agent version 4.5.11 eliminate the need to separately configure the Network Agent in a multi-tenant setup when running multiple nodes on the same machine. If you use the Network Agent version 4.5.7 with Java Agent version 4.5.10 or earlier, you need to configure the Network Agent in a multi-tenant setup. For more details, refer Network Agent and Java Agent Installation Instructions.
  • You can now set up Network Visibility features to monitor Java applications running on Windows operating systems. You need a Network Visibility license to enable and use Network Visibility features. Refer Windows System Requirements for more information.
Resolved Issues
Key
Summary

NETWORK-5025

"File name too long" error is displayed when installing Network Agent
NETWORK-5445

Network Agent with LD_PRELOAD option stops the application from starting up

NETWORK-5430JVMs in WebSphere take longer time to shut down when JAVA web-servers are configured with LD_PRELOAD option

4.5.6 Updates

Network Agent

Version 4.5.6.1690 – November 29, 2018

Enhancements
  • In addition to the performance improvements made in 4.5.4, the Network Agent can now support up to 50 Application Agents running on the same server as that of the Network Agent, in a single tenant or multi-tenant environment.

4.5.5 Updates

Version 4.5.5.1612 – November 13, 2018

Enhancements
  • When installing the Network Agent, you no longer need to unzip the file in the external-services directory. It is now provided in an unzipped format.
Resolved Issues
Key
Summary
NETWORK-4562Possibility of Network Visibility Agent crash when running in Multi-Tenant setup.

4.5.4 Updates

Version 4.5.4.0 – October 25, 2018

Enhancements
  • You can now use Network Visibility to monitor applications running on Kubernetes. For more information, see Network Visibility with Kubernetes.
  • Performance Improvements for Network Agents. Network Agent can now support up to 50 Application containers running on the same node as that of the Network Agent.
Known Issues
  • There is a possibility of Network Visibility Agent crashing when running in Multi-Tenant setup. If you're using a Multi-Tenant setup, you may not want to upgrade to the 4.5.4 agent.
Resolved Issues
Key
Summary
NETWORK-1813Content in Mapping Wizard needs hover-over help text

4.5.2 Updates

Version 4.5.2.1410 – October 9, 2018

Enhancements
  • A new health rule type called Advanced Networks groups metrics related to Network Visibility, such as PIE (performance impact events), zero window, data retransmission, and errors.
Known Issues
  • There is a possibility of Network Visibility Agent crashing when running in Multi-Tenant setup. If you're using a Multi-Tenant setup, you may not want to upgrade to the 4.5.4 agent.

4.5.0 Updates

July 11, 2018

Enhancements
  • Transaction Snapshots now support network analysis and troubleshooting workflows. 
    In the Snapshot Overview, you can right-click on a flow and choose View Network Metrics. The resulting dashboard shows the Performance Impacting Events (top-left chart) for that flow and possible correlating factors for these events.
  • The Network Dashboard can now show Cross Application Flows.
  • The Network Agent now supports monitoring multiple applications running in Docker containers on the same host. You can deploy one Network Agent per host and collect individual metrics for every local application monitored by a Java App Agent in a container. See Docker and Network Visibility.
  • The Network Agent uses packet captures to calculate Network Visibility metrics. You can use the following new Health Rule to troubleshoot packet-capture issues that might affect metrics generated by an agent: 
    Network-Host: Packet drops too high
    This rule triggers an alert when packets get dropped between a Network Agent and the host interface. A high rate of packet drops on the host can result in inaccurate metrics.    
  • The Connection Explorer, Mapping Wizard, and Connections tab (in network link popups) can now display the Fully-Qualified Domain Names for remote services and Load Balancers. This makes it easier to identify the external services used by your monitored applications.
  • Usability enhancements:
    • Right-click dashboard charts now support both linear and logarithmic scales.
    • You can open the Unmapped Connection Wizard directly from a Tier Dashboard if that tier has any unmapped connections.
  • The Network Dashboard uses a new visual convention to represent TCP Endpoints.

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 look at the Connection KPIs. 
  • Network Visibility cannot monitor Cross Application Flows that use Jersey web servlets. As a workaround, you can disable Jersey servlet instrumentation. The impact is that Business Transactions on these flows get recognized as servlets instead of Web Services. To implement this workaround:

    1. Select the application of interest in the Controller UI.
    2. Choose Configuration > Instrumentation > Transaction Detection.
    3. Disable instrumentation for Jersey Servlet and Jersey 2.x Servlet