Configure Application Insights Profiler
Updated Profiler Agent
The trigger features only work with version 2.6 or newer of the profiler agent. If you are running an Azure App Service, your agent will be updated automatically. You can see what version of the agent you are running if you go to the Kudu URL for your website and append \DiagnosticServices to the end of it, like this:
https://yourwebsite.scm.azurewebsites.net/diagnosticservices. The Application Insights Profiler Webjob should version 2.6 or newer. You can force an upgrade by restarting your web app.
If you are running the profiler on a VM or Cloud Service, you need to have Windows Azure Diagnostics (WAD) extension version 16.0.4 or newer installed. You can check the version of WAD by logging onto your VM and looking this directory: C:\Packages\Plugins\Microsoft.Azure.Diagnostics.IaaSDiagnostics\126.96.36.199. The directory name is the version of WAD that is installed. The Azure VM agent will update WAD automatically when new versions are available.
Profiler settings page
To open the Azure Application Insights Profiler settings pane, go to the Application Insights Performance pane, and then select the Configure Profiler button.
That opens a page that looks like this:
The Configure Application Insights Profiler page has these features:
|Profile Now||Starts profiling sessions for all apps that are linked to this instance of Application Insights.|
|Triggers||Allows you to configure triggers that cause the profiler to run.|
|Recent profiling sessions||Displays information about past profiling sessions.|
This option allows you to start a profiling session on demand. When you click this link, all profiler agents that are sending data to this Application Insights instance will start to capture a profile. After 5 to 10 minutes, the profile session will show in the list below.
For a user to manually trigger a profiler session, they require at minimum "write" access on their role for the Application Insights component. In most cases, you get this access automatically and no additional work is needed. If you're having issues, the subscription scope role to add would be the "Application Insights Component Contributor" role. See more about role access control with Azure Monitoring.
Clicking the Triggers button on the menu bar opens the trigger settings box. You can set up trigger to start profiling when the percentage of CPU or Memory use hits the level you set.
|On / Off Button||On: profiler can be started by this trigger; Off: profiler won't be started by this trigger.|
|Memory threshold||When this percentage of memory is in use, the profiler will be started.|
|Duration||Sets the length of time the profiler will run when triggered.|
|Cooldown||Sets the length of time the profiler will wait before checking for the memory or CPU usage again after it's triggered.|
Recent Profiling Sessions
This section of the page shows information about recent profiling sessions. A profiling session represents the period of time when the profiler agent was taking a profile on one of the machines hosting your application. You can open the profiles from a session by clicking on one of the rows. For each session, we show:
|Triggered by||How the session was started, either by a trigger, Profile Now, or default sampling.|
|App Name||Name of the application that was profiled.|
|Machine Instance||Name of the machine the profiler agent ran on.|
|Timestamp||Time when the profile was captured.|
|Tracee||Number of traces that were attached to individual requests.|
|CPU %||Percentage of CPU that was being used while the profiler was running.|
|Memory %||Percentage of memory that was being used while the profiler was running.|
Use web performance tests to generate traffic to your application
You can trigger Profiler manually with a single click. Suppose you're running a web performance test. You'll need traces to help you understand how your web app is running under load. Having control over when traces are captured is crucial, because you know when the load test will be running. But the random sampling interval might miss it.
The next sections illustrate how this scenario works:
Step 1: Generate traffic to your web app by starting a web performance test
If your web app already has incoming traffic or if you just want to manually generate traffic, skip this section and continue to Step 2.
In the Application Insights portal, select Configure > Performance Testing.
To start a new performance test, select the New button.
In the New performance test pane, configure the test target URL. Accept all default settings, and then select Run test to start running the load test.
The new test is queued first, followed by a status of in progress.
Step 2: Start a Profiler on-demand session
When the load test is running, start Profiler to capture traces on the web app while it's receiving load.
Go to the Configure Profiler pane.
Step 3: View traces
After Profiler finishes running, follow the instructions on notification to go to Performance pane and view traces.