According to the Tiers and Nodes document1, establishing standards for naming applications, tiers, and nodes can help you identify and organize the components of your monitored environment, as well as troubleshoot performance issues and health rule violations. Some of the statements about establishing naming conventions are true:
Application Tier and Node values can be configured in the application agent startup script: This is true for Java agents, as you can pass values to the agent that will be used as the application, tier, and node name for the system. For example, you can use the -Dappdynamics.agent.applicationName, -Dappdynamics.agent.tierName, and -Dappdynamics.agent.nodeName properties to specify the names in the JVM startup script2.
Node names must be unique across the entire business application: This is true, as node names are used to identify the individual instances of the application components that are monitored by AppDynamics. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
Application Tier and Node values can be configured in the controller-info.xml file: This is true for Java agents, as you can also configure the names in the controller-info.xml file, which is located in the <agent_home>/conf directory. The controller-info.xml file contains the properties that define the agent identity and connection to the Controller. You can use the <application-name>, , and elements to specify the names in the file2.
Some of the statements about establishing naming conventions are false:
Nodes that reside on different Tiers and different machines (hosts) can have duplicate Node names: This is false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
Nodes that reside on the same Tier but on different machines (hosts) can have duplicate Node names: This is also false, as node names must be unique across the entire business application, regardless of the tier or the host they belong to. Having duplicate node names can cause confusion and errors in the data collection and reporting. Therefore, you should use a naming convention that ensures uniqueness and clarity for each node1.
References:
Tiers and Nodes
Name Business Applications, Tiers, and Nodes
Submit