AppDynamics Application Intelligence Platform

3.9.x Documentation

PDFs

Learn by Watching

Doc Maps

 

This topic discusses naming AppDynamics business applications, tiers, and nodes. For an overview see Mapping Application Services to the AppDynamics Model.

Naming Guidelines

The maximum length of a tier name is 100 characters and the maximum length of a node name is 500 characters.

(warning) Warning: Do not use ampersands (neither "&" nor its XML encoding, "&") in application or other component names.

Node names must be unique across the entire business application.

Naming Components in a Java Environment

When you start an App Agent for Java on a monitored system, you have the option of passing values to the agent that will be used as the application, tier, and node name for the system. Alternatively you can configure names in the controller-info.xml file. Use these guidelines when configuring custom names:

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

AppDynamics names Java nodes automatically; also you can specify your own node names. In a cloud or auto-scale environment, where nodes come and go regularly, it may be best to let AppDynamics give each node a unique name.

For multiple JVMs on a single machine, see: 

See also:

Automatic Naming for Application, Tier, and Node

The Java Agent javaagent command accepts an argument named uniqueID that AppDynamics uses to automatically name the node and tier for this Java Agent. For example, using this command argument AppDynamics will name the node and tier "my-app-jvm1":

-javaagent:<agent_home>/javaagent.jar=uniqueID=<my-app-jvm1>

When uniqueID is used and the application name is not provided either through the system property or in the controller-info.xml, AppDynamics creates a new business application called "MyApp".

The naming mechanism is used by the Java Agent Download Wizard process. See Quick Install.

Naming Components in a .NET Environment

The App Agent for .NET Configuration Utility automatically names the nodes, and you should not change them. See Naming Conventions for .NET Nodes

See also:

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

See also:

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.

Renaming Icon Labels in the UI

Labeling Your Components
Use labels that are recognizable to the people in your group or company.

Default or environment-based names may not be very user-friendly. You can use labels to make nodes and tiers more recognizable.

1. In the Application, Node, or Tier Dashboard, click Actions -> Edit Properties.

2. In the Properties dialog, type a new name.

3. Click Save.

Note: renaming in the UI is not persistent in the configuration. It changes the labels in the UI only.

Learn More