For your .NET Agent your config file resides in {Agent Install Directory}\ProgramData\config\
Doc on Where standard files are: (https://docs.appdynamics.com/display/PRO43/Administer+the+.NET+Agent)
The file is the config.xml file. That determines the agent configuration and how it is reported into the controller.
This is also controlled by how you are having the IIS Nodes Identified. If you are doing it automatically, then see this documentation for how that node name is assigned. https://docs.appdynamics.com/display/PRO43/Name+.NET+Nodes
I would recommend handling this in 1 of 2 ways:
1. Disabled the auto-configuration controlled by the centralized configuration management, by setting
the following property in your config.xml to false:
configuration_mode_deployer="false" However, do be aware this means that then you would need to have your own centralized way of ensuring all of your configurations get updated when changes are made, but this would ALLOW you to change the node names, and then they would not get updated on their own.
2. Is it correct to say that you have your IIS Nodes set to be discovered automatically similar to this setting: <IIS> <automatic /> <applications /> </IIS>
Modify this to specify these settings, rather than try to go into all possible options in this post I recommend reviewing the sepcifics of this here: https://docs.appdynamics.com/display/PRO43/Name+.NET+Nodes
It indicates that this naming of nodes is controlled automatically to follow this convention:
<machine NetBIOS name>-<tier>-<IIS site>/<app>
It does not appear to indicate that you may change this. However, it has been my experience that with proper editing to any of the configuration xml files anything can be modified, but just fair warning, may not be officially supported. Perhaps try manually defining your IIS applications and setting the node names.
Does this answer your inqury?
********Disclaimer*********
Be sure to make a backup of any configuration or changes to files you make prior to modifying for simplified rollback. Also, test any changes in test environment where possible before deploying to a PROD environment.
*********************
... View more
