Network Visibility requires:
- Version 4.4 or higher of the Controller with a Network Visibility license (one license unit per OS instance).
- Each host must have
- A Network Visibility Agent (version 4.4 or higher)
- A Java App Server agent (version 4.4 or higher) with an App Agent license
- You must have
rootaccess permissions on the agent host to install the Network Agent. (You do not need
rootaccess to run the agent.)
- Network Visibility is supported on Linux hosts with Java App Server agents only.
- 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 the following libraries pre-installed:
- This release does not support the following 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, go to the Application Dashboard.
- 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:
- Select the application of interest in the Controller UI.
- Choose Configuration > Instrumentation > Transaction Detection.
- Disable instrumentation for Jersey Servlet and Jersey 2.x Servlet
- See also Network Visibility Known Issues in the Release Notes.