Custom Tier Names

Rather than creating a tier for each virtual application, all virtual applications can report as nodes under a single tier. You can specify the tier name in the AppDynamicsConfig.json file.

Note:
  • When you instrument your application using the .NET Agent site extension, the .NET Agent automatically instruments all virtual directories and applications. However, all AppSettings set at the root app are inherited by all virtual applications.
  • For NuGet-based deployments, the agent uses the AppDynamicsConfig.json file deployed in the same path as the Profiler DLL and ignores the AppDynamicsConfig.json file settings for individual virtual apps in the deployment.

By default, the tier name of the application in the AppDynamicsConfig.json file is null. The following edited version of the AppDynamics.Config.json file shows a tier name of Business App 15. Note that the node name cannot be changed as its value is automatically updated as the application scales vertically and horizontally:

{
"controller": {
"host": "PUT_YOUR_VALUE_HERE",
"port": 0,
"account": "PUT_YOUR_VALUE_HERE",
"password": "PUT_YOUR_VALUE_HERE",
"ssl": false,
"enable_tls12": false,
"proxy": true
},
"application": {
"name": "Demo Multi App",
"tier": "Business App 15",
"node": null
},
"instrumentors": {
"customCorrelationConfig": null,
"enable": [],
"disable": []
}
}

After the application is restarted, the virtual app tier name appears as Business App 15. When you expand the tier on the Tiers & Nodes Dashboard, you see the nodes of the virtual applications and the main (root) application. For example, if an Azure Web App named demomultiapp has three virtual apps (the main application and two sub applications named billing and reports), there is just one tier named Business App 15. Within that tier, there are three nodes: RD001550D5449FA-demomultiapp, RD001550D5449FA-demomultiapp/billing, and RD001550D5449FA-demomultiapp/reports.

The Nodes Dashboard displays the nodes of the tier Business App 15 in a similar manner. Nodes of the virtual application are displayed in the Controller UI using the name of the virtual machine the app is running on, followed by the name of the virtual application as it appears in Azure Web Apps.

Note: The current agent configuration file does not support targeting different virtual applications for customized tier naming, however, you can manually create .NET tiers and move the nodes to different tiers in the Controller UI.