Profile live Azure Service Fabric applications with Application Insights

You can also deploy Application Insights Profiler on these services:

• Azure App Service
• Azure Cloud Services
• Azure Virtual Machines

Set up the environment deployment definition

Application Insights Profiler is included with Azure Diagnostics. You can install the Azure Diagnostics extension by using an Azure Resource Manager template for your Service Fabric cluster. Get a template that installs Azure Diagnostics on a Service Fabric Cluster.

To set up your environment, take the following actions:

1. Profiler supports .NET Framework and .Net Core. If you're using .NET Framework, make sure you're using .NET Framework 4.6.1 or later. It's sufficient to confirm that the deployed OS is Windows Server 2012 R2 or later. Profiler supports .NET Core LTS and newer applications.

2. Search for the Azure Diagnostics extension in the deployment template file.

3. Add the following SinksConfig section as a child element of WadCfg. Replace the ApplicationInsightsProfiler property value with your own Application Insights instrumentation key:

   "SinksConfig": {
     "Sink": [
       {
         "name": "MyApplicationInsightsProfilerSink",
         "ApplicationInsightsProfiler": "00000000-0000-0000-0000-000000000000"
       }
     ]
   }
   

   For information about adding the Diagnostics extension to your deployment template, see Use monitoring and diagnostics with a Windows VM and Azure Resource Manager templates.

4. Deploy your Service Fabric cluster by using your Azure Resource Manager template.
   If your settings are correct, Application Insights Profiler will be installed and enabled when the Azure Diagnostics extension is installed.

5. Add Application Insights to your Service Fabric application.
   For Profiler to collect profiles for your requests, your application must be tracking operations with Application Insights. For stateless APIs, you can refer to instructions for tracking Requests for profiling. For more information about tracking custom operations in other kinds of apps, see track custom operations with Application Insights .NET SDK.

6. Redeploy your application.

Next steps

• Generate traffic to your application (for example, launch an availability test). Then, wait 10 to 15 minutes for traces to start to be sent to the Application Insights instance.
• See Profiler traces in the Azure portal.
• For help with troubleshooting Profiler issues, see Profiler troubleshooting.