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

Skip to end of metadata
Go to start of metadata
On this page:

Related pages:

By default the AppDynamics .NET Agent (agent) automatically names nodes using a combination of the Windows machine name, the tier name, and the name of the .NET application.

(info) If you are upgrading from the .NET Agent version 3.7.7 or earlier, the new node naming convention takes effect upon restart. Nodes named under the old scheme become historical nodes with no correlation to new nodes.

Name IIS Nodes Automatically

The agent names IIS nodes as follows:

<machine NetBIOS name>-<tier>-<IIS site>/<app>

The agent omits app when the application is the root application for the IIS site.
The agent omits tier when the tier name is the same as the IIS site name.

For example:

WIN-86M7CEJO6P5-Order Server-OrderSvc

WIN-86M7CEJO6P5 is the machine NetBIOS name.
Order Server is the tier name.
OrderSvc is the IIS site name. The application is the site root, so the agent omits the application name.

For another example:

WIN-86M7CEJO6P5-Order Server-Store/ProcessOrder

Store is the IIS site name.
ProcessOrder is the application name within the site.

(info) Different .NET versions of the same application have their own versions of the CLR and run on independent processes. Therefore the agent identifies the two processes as different nodes.

IIS Web Gardens

The syntax for web gardens is the same as IIS Nodes, except that the agent appends a zero-based process index to differentiate the worker processes.

<machine NetBIOS name>-<tier>-<IIS site>/<app>-<process index>

When IIS first launches web garden processes, the agent assigns a sequential index to each process. However when IIS recycles a process, the agent reuses the available index freed by the terminated process. Therefore there is no correlation between the index sequence and the chronological start of the process.

Sometimes you may see more nodes than the maximum number of worker processes. This can happen when a long-running request prevents a process from shutting down before its replacement launches.

Name Windows Service or Standalone Application Nodes Automatically

The agent names Windows service and standalone application nodes as follows:

<machine NetBIOS name>-<tier>-<Windows service name or executable name>

The agent omits tier when the tier name is the same as the service name or executable name.

For example:


WIN-86M7CEJO6P5 is the machine name.
MyWindowsService is the the Windows service name.

For another example:


WIN-86M7CEJO6P5 is the machine name.
MyStandaloneApp.exe is the executable file name.