AppDynamics Application Intelligence Platform
This topic describes the conventions that the App Agent for .NET uses to automatically name nodes.
Node naming relies on the application name to directly link nodes to an application. This naming convention clarifies node names for applications in an application pool hosting multiple applications and node names for applications in a recycle process.
If you are upgrading to 3.8 from the App Agent for .NET 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 the new nodes.
The naming pattern for IIS nodes is as follows:
Machine name is the NetBIOS name of the local computer where the application runs.
Tier is the name of the logical tier for the application. See Logical Model.
Site is the IIS Site name.
App is the virtual path within the site.
The syntax for web gardens is the same as IIS Nodes, except that we append a process index to differentiate between the worker processes in the web garden.
The process index represents the zero-based index of the process. For a web garden-IIS-hosted application with five worker processes, the index could be 0, 1, 2, 3 or 4.
Don't confuse the process index with the Windows process id.
When IIS first launches web garden processes, the agent assigns a sequential index to each process. However, as IIS recycles processes, the agent reuses the available indexes freed by terminated processes. This means there will likely be no correlation between the index sequence and the chronological start of the process.
There are edge cases where 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.
The naming pattern for Windows service nodes is as follows:
Machine name is the NetBIOS name of the local computer where the Windows service runs.
Service name is the same as Service name in the service properties window.
The naming pattern for standalone applications is as follows:
Machine name is the NetBIOS name of the local computer where the standalone application runs.
Executable name is the standalone application executable file name.
Below is the algorithm for calculating how many nodes will be generated. It refers to all nodes that are alive, as historical node counts can change via retention and deletion time frames as well as manual deletion, etc.
Self-Hosted Process (Windows Service, Console Application, etc)
Number of Nodes
In the case of a webgarden, by default AppDynamics flags a node as historical within five minutes after it recycles. Wait 5 minutes for a recycled node to disappear from the application flow map.