AppDynamics Application Intelligence Platform
The App Agent for .NET requires information about your .NET applications: IIS applications, Windows services, or standalone applications. Configure the App Agent for .NET according to what kind of application you want to monitor:
Use the App Agent for .NET Configuration Utility to configure the agent just after installation, or to make changes to existing agent configurations.
AppDynamics recommends that you install the Controller, or have access credentials to a SaaS Controller, before installing an agent.
Prior to configuration, run the .NET Agent Installer. See Install the App Agent for .NET.
The utility configures one agent at a time.
AppDynamics implements the profile API of the .NET CLR. Since a Windows machine only allows use of one profiler at a time, you must uninstall any pre-existing profiler, such as Ant, VS 2010 Performance Tools, or others. The utility alerts you if it finds a pre-existing profiler.
To apply configurations, the .NET Agent Configuration Utility must restart IIS. The utility offers you the option to restart IIS or not. If you choose not to restart, configurations apply the next time IIS restarts.
For the App Agent for .NET to instrument your application correctly, ensure the following Windows accounts have the required file system access permissions:
The required permissions are as follows:
C:\Program Files\AppDynamics\AppDynamics .NET Agent
1. In the Windows menu, click AppDynamics -> .NET Agent -> AppDynamics Agent Configuration.
2. If the "Warning: 3rd Party Profiler installed" message displays, it means that the configuration utility has discovered another profiler. Windows only allows one profiler per machine. Because AppDynamics uses a profiler you must uninstall any other profilers.
Click Yes to exit and uninstall any pre-existing profiler. Check the registry to make sure that the uninstall process cleaned up the registry entries. Use the warning message to identify any undeleted profiler environment variables.
3. When the configuration utility detects legacy agent configurations from version 3.7.7 or earlier, it displays the Upgrade Configuration window.
Removing legacy configurations modifies web.config files causing IIS to restart affected applications.
4. When the utility discovers no further profiler conflicts or after any configuration clean up, the welcome window displays.
Click Next to advance to Log directory permissions.
The first window helps you set up the location of the agent logs and provide the correct account access to the logs.
1. If you want to change the default location of the log directory, click Change and select a new location.
The default logs directories are as follows:
Windows Server 2008 and later:
Windows Server 2003:
2. If needed, add accounts for log directory permissions.
Commonly-used accounts are provided. If your application uses another account, enter the Windows account you use to run your web application as defined by its application pool or the Windows service account. The account name must be valid on the operating system and have permission to write to the log files directory.
3. Click Add. If you get a warning message, make sure that the account is valid on the system.
4. Click Next and the wizard confirms the list of accounts.
5. Click Next to advance to Controller Configuration.
1. Enter the Controller access information and credentials.
2. Click Test Controller Connection to verify the connection.
3. Click Next to advance to the Application Configuration
AppDynamics retrieves existing business application information from the Controller and displays it in the left column. Controller connection status displays on the right.
4. Click Existing Applications from the Controller to select business applications from the Controller.
If you haven't defined business applications in the Controller, the utility displays an empty list.
Click New Application to define a new business application. Be careful about spellings and capitalization and note down the exact name.
Do not use ampersands in the business application name; they are not supported at this time.
5. Click Next to advance to Assign IIS applications to tiers.
1. Read about how AppDynamics uses business applications, tiers, and nodes to organize application performance monitoring. In summary:
See Logical Model.
2. Decide how to identify and name the tiers. Either AppDynamics will automatically configure tier names, or you can manually configure them.
Use these guidelines for deciding whether to use automatic or manual naming:
AppDynamics names tiers using this pattern:
1. In the Assign IIS applications to tiers window click Automatic.
2. If prompted, click OK to confirm Automatic configuration.
The configuration utility summarizes the configuration settings.
3. By default when you click Next the configuration utility restarts IIS.
If you do not want to apply the configuration right away, uncheck the box. The Configuration Utility saves the information and applies it the next time you restart IIS.
4. If you proceed and click Next, the configuration utility logs its activities, including stopping and restarting IIS, and reports any problems. Review the summary for any issues in red font. Green font indicates the more interesting logged events. The summary shows any Warnings (W) or Errors (E). If you have errors, contact AppDynamics Support.
5. When there are no errors, click Next.
6. Click Done to close the Configuration Utility.
1. In the Assign IIS applications to tiers window click Manual, then click Next.
2. Assign IIS Applications to AppDynamics tiers.
Select a tier on the right and click a business application on the left. The assigned tier will be highlighted in boldface.
For large IIS installations, use the Max IIS tree depth pulldown to display all the projects. A large tree depth may take some time to view.
To create new tiers, enter a name and click Add Tier.
5. When you are done click Next. AppDynamics displays a configuration summary.
6. Review the configuration. If you need to make changes click Back.
7. On the Configuration Summary window, un-check Restart IIS if you don't want to immediately restart IIS.
You may restart later to apply your changes, or they will take effect after a reboot.
7. If you proceed and click Next, the Configuration Utility logs its activities, including stopping and restarting IIS, and reports any problems.
8. Review the configuration log summary.
As it applies the configuration, AppDynamics generates a log of the configuration activities and displays a summary. Review the summary for any issues in red font. Green font indicates the more interesting logged events. The summary shows any Warnings (W) or Errors (E). If you have errors, contact AppDynamics Support.
9. Click Next. The wizard completes.
For troubleshooting information see Resolve App Agent for .NET Installation and Configuration Issues.
You can set up a .NET Agent configuration file and run it from the command line. This is useful when you have multiple agents to configure.
1. From a command line, start the configuration utility:
The utility starts.
2. Configure the agent as described in the previous sections. The configuration is applied.
In addition, when the configuration completes, AppDynamics creates a setup file.
Use this setup file as an argument to the command line utility.
1. Start the .NET Configuration Utility from the command line. Change the file path and setup file path as needed.
The utility runs in command line mode; the user interface does not launch.
When it finishes, the utility exits the process with status 0 for success or any other number for failure.
2. Review the Winston.txt log file in the default logs directory for details.