View Source

Install the NuGet package AppDynamics.Agent.Azure.AppService.Windows to add the .NET microservices agent directly to projects you plan to deploy to Windows Azure. This package works for Azure App Service (formerly Azure Websites): Web Apps and API Apps.

Prepare to Install the NuGet Package

To install the for Windows Azure NuGet package you need:

Connection information for your Controller
Visual Studio >= 2012
A Visual Studio solution to monitor
Windows Azure SDK
Windows Azure account

These instructions assume you are familiar with NuGet package management in Visual Studio and with the Microsoft Azure Portal. You can also try the step-through tutorial on how to instrument an App Service on the community knowledgebase.

Add the .NET Microservices Agent to Your Azure Solution

Use the NuGet package manager to browse the nuget.org package source and install the AppDynamics.Agent.Azure.AppService.Windows package to your Azure solution in Visual Studio.

For details about managing NuGet packages, see the documentation for your version of Visual Studio.

The AppDynamics.Agent.Azure.AppService.Windows package installation prompts you as follows:

The installer may ask you to verify your changes. If so, click OK.
Click I accept to agree to the terms of the license.
In the Solution Explorer, select the AppDynamicsConfig.json file.

Enter the connection information for your Controller in the area on the left, in JSON format.
For example:

{
  "controller": {
    "host": "PUT_YOUR_VALUE_HERE",
    "port": 0,
    "account": "PUT_YOUR_VALUE_HERE",
    "password": "PUT_YOUR_VALUE_HERE",
    "ssl": false,
    "enable_tls12": false
  },
  "application": {
    "name": "PUT_YOUR_VALUE_HERE"
  }
}

Configure the Controller Connection

You have the following options to configure the .NET Agent to connect to the Controller:

During development: As shown in the previous screenshot, you can enter your environment variables in the AppDynamicsConfig.json file, and save it in source control.
During build: Define your msbuild parameters or environment variables that are passed to the AppDynamicsConfig.json file at build time. AppDynamicsConfig.json does exist at build time. So, if you're defining your msbuild parameters/env variables at build time, you will need to ignore it in source control so that the new AppDynamicsConfig.json file will be created.
During runtime: Enter your environment variables in Azure.

By default, the .NET microservices agent names Azure tiers as site name. The .NET microservices agent names Azure nodes by machine name appended with the website hostname.