Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor edits


  1. Open the wizard from the home page in the controller UI by clicking Getting Started.
  2. Enter the configuration values for the application instance as described in the wizard. You name the node and indicate the tier and business application to which it will belong. If you 're are not sure of the best values to use, you can use temporary names and change them later.
  3. When finished, download the agent. How you download the agent varies by agent type. In most cases, the agent comes as a ZIP file that you extract and install in the startup routine of your server. For other types of agents, you may need to modify the instrumented source code, for example, by including the agent library. The wizard walks you through it for each agent type.
  4. Install the agent on your app server.  
  5. Apply load to your application. If you are instrumenting a production application, this will happen with customer interaction. Otherwise, create some test load on your application. The agent instruments the application code and reports metrics back to the Controller.
  6. View your application in the Application Dashboard, for . For example: 

The wizard makes it easy to perform a basic installation of the agent with minimal minimally required settings, such as the controller Controller host and port, SSL, application name, and tier name. For advanced options or more complicated scenarios, you need to perform a manual installation of the agent. For more information, see the agent-specific link in the following section.    


  • If the nodes reside on the same tier, but on different machines.
  • If the nodes reside on the same machine, but on different tiers.
  • Node names and machine names must unique. When a node is registered to a controller, it is associated with the machine it is on, and cannot be moved to another machine without changing the node name. 


  1. The approximate bandwidth used by a single Java Agent with the default configuration is 5 five to 8 eight kilobytes per second. 
  2. Scaling of additional agents is linear. That is, if the average bandwidth usage for an app agent in a given deployment is 5 kilobytes, adding 10 means that bandwidth usage will be 5 × 10, or 50 kilobytes.   
  3. While the average bandwidth used is 5 five to 8 kbytes eight kbytes per second, agents send data to the Controller in bursts rather than as a steady stream of data. When testing bandwidth usage, to determine the actual kbytes per second used by an agent, you need to observe and average out traffic over the course of at least several minutes. 
  4. When testing bandwidth usage in the environment, keep in mind that different types of tiers will generate a different amount of load. For instance, a database tier tends to generate more traffic between the agent and Controller than an application server tier. For the best possible estimate, the test should take this into account.

Agent License Considerations

For agent-based license units (including units—including APM, database monitoring, and server monitoring), licenses monitoring—licenses are allocated to the first agents that register with the Controller up to the licensed limit. For example, with five agent licenses, the first five agents that connect to the Controller are licensed.  

Agent licenses are not bound to a particular machine or application. Therefore, a transfer of an agent-based license can be done simply by shutting down the application that runs the licensed agent (uninstalling agent—uninstalling the agent if the application will need to be restarted) and restarted—and starting up the new application with the newly installed agent. Once the agent disconnects, a license unit is freed for the second agent.

For application monitoring agents (Java, .NET, Node.JS, and so on), a license validation cycle runs every five minutes. It causes the agents to connect and validate that available license units are not exceeded. Historical usage data is captured during this cycle and stored as 5five-minute usage data. Every hour, the 5five-minute usage data is rolled up in hour usage data, which includes data on license unit usage. The five-minute data is purged after a few hours.