This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.


On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
50 rates

This topic discusses naming AppDynamics business applications, tiers, and nodes. For an overview see AppDynamics Concepts.

Tier and Node Naming Guidelines

While node names do not need to be unique within a business application, the combination of tier and node name must be unique for the business application. Put another way, a tier cannot have two nodes with the same name. The tier names in a business application must also be unique.  

The maximum length of a tier name is 100 characters and the maximum length of a node name is 500 characters. Do not use ampersands ("&" or "&") in application or other component names.

Naming Components in a Java Environment

When you start a JVM with the Java Agent, you have the option of passing values to the agent in several ways, including as system properties, environment variables, or in the controller-info.xml file. 

It's possible to install the Java Agent from a single agent home directory to multiple JVMs. However, you'll need to differentiate some of the configuration settings for each agent instance. You can do so with these guidelines:

  • Configure items that are common for all the nodes in the controller-info.xml file.
  • Configure items that are unique to a node in the JVM startup script.

AppDynamics names Java nodes automatically, but you can override the default name with a name you specify. In a cloud or automatically scaling environment where nodes come and go regularly, it may be best to allow automatic naming to give each node a unique name.

Naming Components in a .NET Environment

The AppDynamics Agent Configuration utility for the .NET Agent lets you name IIS tiers automatically or manually. You must edit the config.xml configuration file to name Windows service or standalone application tiers. See Name .NET Tiers. By default the agent automatically names nodes. See Name .NET Nodes.

Naming Components in a PHP Environment

A PHP runtime instance maps to a node. Your naming convention may depend on your exact environment.  Use a name that clearly identifies the Web service that corresponds to the node. Some options are:

  • hostName-appName-nodeName
  • hostName-tierName-nodeName
  • appName-nodeName
  • tierName-nodeName
  • IP address
  • fully qualified domain name

Naming Components in a Node.js Environment

A Node.js process maps to an AppDynamics node. The nodes are named by combining the prefix that you specify for the nodeName in the requires statement that you add to the application source code when you install the Node.js agent with a hyphen and a digit. See Modifying the Application Code.

For example, if you designate a prefix of MyNode for the nodes in the MyTier tier, the nodes in that tier are named MyNode-0, MyNode-1, MyNode-2 and so on.

Naming Web Server Components

A web server instance maps to a node. Your naming convention may depend on your exact environment.  Use a name that clearly identifies the web server that corresponds to the node. Some options are:

  • hostName-appName-nodeName
  • hostName-tierName-nodeName
  • appName-nodeName
  • tierName-nodeName
  • IP address
  • fully qualified domain name


  • No labels