Install AppDynamics for Windows Azure with NuGet

On this page:

Related pages:

Monitor your Azure cloud solutions with the AppDynamics for Windows Azure NuGet package. Sign up for the AppDynamics add-on in the Windows Azure portal, then enable the AppDynamics agent in your Visual Studio solution.

Requirements

The AppDynamics for Windows Azure Nuget package requires the following:

Visual Studio 2010 or later
A Visual Studio solution to monitor
Visual Studio must have the following permissions to the solution:
- Read and Write permissions to each project directory
- Read and Write permissions to each Visual Studio .NET C# Project (*.csproj) file
- Read and Write permissions to the Service Definition (ServiceDefinition.csdef) file
Windows Azure SDK
Windows Azure account
If the Visual Studio Standalone Profiler is installed, you must uninstall it and remove related registry entries.

Register for an AppDynamics for Windows Azure Account

If you haven't registered for an AppDynamics account, see Register for AppDynamics for Windows Azure.

Once you've registered, we will send you a Welcome email with your URL and credentials to connect to the AppDynamics Controller. If you already have AppDynamics credentials from another product, you can sign in using them.

Add the .NET Agent to Your Azure Solution

Use the NuGet package manager to add the .NET Agent to your Azure solution in Visual Studio.

In Visual Studio, right-click your solution name and chose Manage NuGet Packages for Solution.
Show this step in Visual Studio
Click the NuGet official package source in the left menu and type "AppDynamics" in the search bar in the upper right.
Select AppDynamics .NET Agent for Azure and click Install.
Show this step in Visual Studio
Click the projects you want to monitor, then click OK.
Show this step in Visual Studio
Click I Accept to agree to the license terms.
Show this step in Visual Studio
Enter the connection information from your Welcome email:
Controller Host
Controller Port
Account Name
Account Key
AppDynamics automatically populates Application Name with the name of your Windows Azure solution.
Show this step in Visual Studio
You can also find your Account name and key in the AppDynamics Controller under Settings -> License.
Close the Manage NuGet Packages window.
Verify the following:
- Instrumented projects have an AppDynamics folder.
- The AppDynamics folders contain an MSI installer package, a config.xml, and a setup.cmd file.
- The ServiceDefinition.csdef has an AppDynamics startup task.
Show this step in Visual Studio
By Default the .NET Agent names Azure tiers for the role name. For example "AzureEmailService". If you want to customize the tier name, follow the steps under Customize Tier Names for Azure Roles before you publish the Windows Azure cloud solution.
Right-click the Windows Azure cloud solution and click Publish.
Show this step in Visual Studio

Once you've successfully published your project, you're ready to log on to the Controller and begin monitoring your solution!

Update Agent Configuration

New in 4.0.1, if you have already published your solution, you can update the .NET Agent configuration for the currently installed version without upgrading the agent.

Edit the config.xml file to make configuration changes.
Edit the startup.cmd file.
Set the CONFIGUPDATE variable to "true".
```
SET CONFIGUPDATE=true
```
Publish the Windows Azure cloud solution

Customize Tier Names for Azure Roles

By default the .NET Agent names tiers for Windows Azure role names. For example: MvcWebRole. If you want to customize the tier name for a role, edit the config.xml to specify the tier name using a regular expression for the IIS site.

Edit the config.xml in Visual Studio.

Replace the IIS element with the following code block:

<IIS>
  <applications>
    <!-- Configure IIS tier names with a regular expresson. -->
    <application path="/" site="" site-regex="true">
        <tier name=""/>
    </application>
  </applications>
</IIS>

Enter a regular expression for the Application site attribute. For example for a role named "MvcWebRole":
```
<application path="/" site="MvcWebRole.*" site-regex="true">
```
Specify a tier name. For example:
```
<tier name="My Azure Tier"/>
```
Save changes to the config.xml and repeat the process for other roles.
Publish the Windows Azure cloud solution.

If you previously published your solution using automatic tier naming, you may need to delete your deployment for the .NET Agent to use the new tier naming scheme.

Sample Azure IIS Application Configuration

<?xml version="1.0" encoding="utf-8"?>
<appdynamics-agent xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <controller host="nativedemocon1.cloudapp.net" port="8090" ssl="false">
    <application name="AzureEmailService" />
    <account name="customer1" password="SJ5b2m7d1$354" />
  </controller>
  <machine-agent />
  <app-agents azure="true" azure-role-name="" azure-role-instance-id="">
    <IIS>
        </applications>
             <!-- Configure IIS tier names with a regular expresson. -->
             <application path="/" site="MvcWebRole.*" site-regex="true">
                  <tier name="My Azure Tier"/>
             </application>
        </applications>
    </IIS>
    <standalone-applications>
         <standalone-application executable="WaWorkerHost.exe">
             <tier name="" />
        </standalone-application>
    </standalone-applications>
  </app-agents>
</appdynamics-agent>