PDFs

On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
55 rates

You can set up the Network Agent to monitor multiple application nodes that are associated with the same IP address because they run on the same physical or virtual server. The Network Agent can calculate unique network metrics for each node individually (rather than at the host level, like traditional tools).

Note the following:

  • If you do not set up the Network Agent as described below, the network metrics for each monitored node will be based on all ingress/egress traffic for the network IP address of the server.
  • 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 following steps outline the workflow:

Check System Requirements

See Network Visibility Requirements and Important Notes.

Stop each Monitored Application

Stop each application of interest if it is monitored by an installed App Agent. You will restart each application after you install and set up the Network Agent.

Install the Network Agent

Install the agent based on the package: 

ZIP Network Agent

 Click here to expand...

You can install the agent using the Standalone Machine Agent or the Network Agent ZIP.

Install using the Standalone Machine Agent ZIP

(New in 4.4.2) You can install the Network Agent as an extension using the Standalone Machine Agent installer. This option is available on Linux 32-bit and 64-bit ZIP installers, version 4.4.2 or higher, only.

  1. Check System Requirements: See Network Visibility Requirements and Important Notes.
  2. If you are installing the Network Agent as part of the Multi-Tenant Install workflow, stop each application of interest if it is monitored by an installed App Agent. You will restart each application after you install and set up the Network Agent.
  3. Install the Standalone Machine Agent using the Linux ZIP installer as described in the Linux Install Using ZIP with Bundled JRE page.
  4. Run the install script using sudo
         cd <standalone-machine-agent-home>/NetVizExtension/agent/
         sudo ./install.sh 
  5. Enable the NetVizMonitoring extension:
    1. Open the following file in a plain-text editor such as vi or Notepad++: 
           <standalone-machine-agent-home>/NetVizExtension/conf/netVizExtensionConf.yml
    2. Set the start setting to true and save the file.
  6. Start the Standalone Machine Agent. The NetVizMonitoring extension should then start automatically. To start the agent on Linux: 
         <machine_agent_home>/bin/machine-agent -d -p <machine_agent_home>/pidfile 
  7. Verify that the Network Agent is running:  
         <standalone-machine-agent-home>/NetVizExtension/agent/bin/appd-netviz.sh status 
    The output provides the process ID (PID) of the Network Agent process.
    If you experience any problems or issues, see FAQs for Network Visibility.
  8. If you are installing the Network Agent as part of a Set Up Network Visibility workflow, proceed to the next step in the workflow:
Install using the Network Agent ZIP
  1. Check System Requirements: See Network Visibility Requirements and Important Notes.
  2. If you are installing the Network Agent as part of the Multi-Tenant Install workflow, stop each application of interest if it is monitored by an installed App Agent. You will restart each application after you install and set up the Network Agent.
  3. Verify that you have sudo or root access permissions on the host where you want to install the network agent. (You do not need sudo or root access to run the agent.)
  4. Open a command prompt on the host, run the mount command, and check the mounted filesystem for the directory where you plan to install the agent. The filesystem should not have the noexec and nsuid flags set.
  5. Download the network-agent package to the machine. 
  6. In a terminal window, cd to the folder where you downloaded the Network Agent ZIP package.
  7. Enter the following command, where <network_agent_home> is the folder where you want to install the agent software:
    unzip <installer.zip> -d <network_agent_home>

    The parent path should not include any directory names with spaces:

    /opt/appdynamics/networkVisibility (OK)

    /opt/appdynamics/network visibility (invalid)

  8. Run the following commands as the administrator or root user on the host machine:
    1. The following command is required only if you are logged in as a different user from the one that will configure and run the agent: 
       chown -R <network-agent-user-group>:<network-agent-user> <network-agent-home>
    2. Go to <network_agent_home> and run the install script:
      cd<network-agent-home>
         ./install.sh
  9. Start the agent by running the following command as the <network_agent_user>:
    <network-agent-home>/bin/start.sh
  10. Verify that the Network Agent is running:
    1. Identify the agent process: <network-agent-home>/bin/appd-netviz.sh status 
      The output provides the process ID (PID) of the Network Agent process.
    2. If you experience any problems or issues, see FAQs for Network Visibility.
  11. If you are installing the Network Agent as part of a Set Up Network Visibility workflow, proceed to the next step in the workflow:

 

RPM Network Agent

 Click here to expand...

  1. Check System Requirements: See Network Visibility Requirements and Important Notes.
  2. If you are installing the Network Agent as part of the Multi-Tenant Install workflow, stop each application of interest if it is monitored by an installed App Agent. You will restart each application after you install and set up the Network Agent.
  3. Verify that you have sudo or root access permissions on the machine where you want to install the network agent. (You do not need sudo or root access to run the agent.)
  4. Open a command prompt on the host, run the mount command, and check the mounted filesystem for the directory where you plan to install the agent. The filesystem should not have the noexec and nsuid flags set.
  5. Download the network-agent package to the machine. 
  6. Verify that you have sudo or root access permissions on the machine where you want to install the agent.
  7. Download the agent package to the machine.
  8. Open a terminal window and enter the following command: sudo rpm -ivh <installer.rpm>
    The network agent software is installed under /opt/appdynamics/netviz.  
  9. To start the agent, enter the following command: sudo service appd-netviz start
  10. Verify that the Network Agent is running: sudo service appd-netviz status 
  11. If you experience any problems or issues, see FAQs and Troubleshooting for Network Visibility.
  12. If you are installing the Network Agent as part of a Set Up Network Visibility workflow, proceed to the next step in the workflow:

DEB Network Agent

 Click here to expand...

 

  1. Check System Requirements: See Network Visibility Requirements and Important Notes.
  2. If you are installing the Network Agent as part of the Multi-Tenant Install workflow, stop each application of interest if it is monitored by an installed App Agent. You will restart each application after you install and set up the Network Agent.
  3. Verify that you have sudo or root access permissions on the machine where you want to install the agent. (You do not need sudo or root access to run the agent.)
  4. Open a command prompt on the host, run the mount command, and check the mounted filesystem for the directory where you plan to install the agent. The filesystem should not have the noexec and nsuid flags set.
  5. Download the agent package to the machine.
  6. Enter the following command:
    sudo dpkg -i <installer.deb>
    The network agent software is installed under /opt/appdynamics/netviz
    The agent should start automatically with the following message: appd-netviz start/running. process <pid #>
    To verify the Network Agent status, run the following: sudo service appd-netviz status 
  7. If the agent does not start, run the following:  sudo service appd-netviz start 
  8. If you experience any problems or issues, see FAQs and Troubleshooting for Network Visibility.
  9. If you are installing the Network Agent as part of a Set Up Network Visibility workflow, proceed to the next step in the workflow:


Set Up the Network Agent

 After you install the Network Agent, do the following:

  1. Open the following file in a text editor: <network_agent_home>/conf/agent_config.lua
  2. Set the enable_netlib option (under npm_config):

    npm_config = {
          log_destination = "file",
          log_file = "agent.log",
          debug_log_file = "agent-debug.log",
          disable_filter = 1,
          mode = "advanced",
          enable_netlib = 1,
          lua_scripts_path = ROOT_DIR .. "/scripts/netagent/lua/",
    }


Set Up each App Agent

After you install and set up the Network Agent, do the following for each App Agent:

Install or Update the App Agent (if needed)

The Network Agent requires version 4.4 or higher of the Java App Server Agent. Update each App Agent that is running an earlier version. See Install the Java Agent.

Configure the App Agent
  1. Navigate to the following folder: <app-agent-install-dir>/<version-number>/external-services
  2. Extract the netviz.zip archive so that the ZIP contents are under the following folder: 
        <app-agent-install-dir>/<version-number>/external-services
  3. Configure the Java App Server Agent startup command to include the LD_PRELOAD environment variable and the appdynamics.socket.collection.bci.enable system property. 
     

     Click here to expand...

    You must set LD_PRELOAD for the Network Agent to collect network metrics for each individual node (rather than for the entire host).  
    You must enable appdynamics.socket.collection.bci.enable for the agent to map network metrics to application flows:

    LD_PRELOAD=/<network-agent-home>/lib/appd-netlib.so \ 
    java -javaagent:<app_server_agent_home>/javaagent.jar \
    -Dappdynamics.socket.collection.bci.enable=true

    The following examples illustrate how editing the agent startup command can differ, depending on the framework of the monitored application. For more information, see the relevant section under Agent Installation by Java Framework and the relevant framework documentation.

    FrameworkExample (App Agent ZIP)
    IBM WebSphere and InfoSphere

    In the WebSphere/InfoSphere UI, navigate to the Java Virtual Machine properties page for the monitored server. Then add javaagent and appdynamics.socket.collection.bci.enable=true as a Generic JVM argument. For example:

    javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true

    You can add LD_PRELOAD as a JVM environment variable. The following example describes how to add an environment variable on a Cognos server using IBM Connections 6.0.0:

    1. Log in to the WebSphere Application Server administrative console of the Cognos server.
    2. Click Servers > Server Types > WebSphere application servers.
    3. Click the cognos_server link.
    4. Click JAVA and then Process Management- >Process definition > Environment Entries.
    5. Click New to add the following entry: LD_PRELOAD=/usr/appd/agents/netviz/lib/appd-netlib.so
    Apache Tomcat

    Add the full command as a Catalina environment variable in file CATALINA_BASE/bin/setenv.sh (Tomcat 6 and later). For example:

    export CATALINA_OPTS="$CATALINA_OPTS LD_PRELOAD=/usr/appd/agents/netviz/lib/appd-netlib.so -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true"
    Glassfish

    Add the full command as a -javaagent JVM option in the GlassFish domain. You can add the agent using the asadmin tool. For example: 

    glassfish4\bin\asadmin create-jvm-options "LD_PRELOAD=/usr/appd/agents/netviz/lib/appd-netlib.so  -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true"
    JBoss Standalone

    Add the full command to the standalone.sh file. For example:

    export JAVA_OPTS="$JAVA_OPTS LD_PRELOAD=/usr/appd/agents/netviz/lib/appd-netlib.so -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true"

    Jetty

    Add the full command to the start.ini config file in the Jetty base directory. For example:

    --exec
    LD_PRELOAD=/usr/appdynamics/agents/netviz/lib/appd-netlib.so -javaagent:/usr/appd/agents/apm/javaagent.jar -Dappdynamics.socket.collection.bci.enable=true

     




  4. To verify that the App Agent is running correctly, enter the following command:
    strings /proc/<app_pid>/environ

    The resulting output should include an entry for LD_PRELOAD, such as: LD_PRELOAD=/<network-agent-home>/lib/appd-netlib.so

 

Start or Restart each Monitored Application

Restart each application that you stopped before you started the Network Agent.

 

  • No labels