You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Profile production apps in Azure with Application Insights Profiler
3
-
description: Identify the hot path in your web server code with a low-footprint profiler
3
+
description: Identify the hot path in your web server code with a low-footprint profiler.
4
4
ms.contributor: charles.weininger
5
5
ms.topic: conceptual
6
6
ms.date: 07/15/2022
@@ -9,34 +9,34 @@ ms.reviewer: jogrima
9
9
10
10
# Profile production applications in Azure with Application Insights Profiler
11
11
12
-
Diagnosing performance issues can prove difficult, especially when your application is running on production environment in the cloud. The cloud is dynamic, with machines coming and going, user input and other conditions constantly changing, and the potential for high scale. Slow responses in your application could be caused by infrastructure, framework, or application code handling the request in the pipeline.
12
+
Diagnosing performance issues can be difficult, especially when your application is running on a production environment in the cloud. The cloud is dynamic. Machines come and go, and user input and other conditions are constantly changing. There's also potential for high scale. Slow responses in your application could be caused by infrastructure, framework, or application code handling the request in the pipeline.
13
13
14
-
With Application Insights Profiler, you can capture and view performance traces for your application in all these dynamic situations, automatically at-scale, without negatively affecting your end users. The Profiler captures the following information so you can easily identify performance issues while your app is running in Azure:
14
+
With Application Insights Profiler, you can capture and view performance traces for your application in all these dynamic situations. The process occurs automatically atscale and doesn't negatively affect your users. Profiler captures the following information so that you can easily identify performance issues while your app is running in Azure:
15
15
16
-
-The median, fastest, and slowest response times for each web request made by your customers.
17
-
- Helps you identify the “hot” code path spending the most time handling a particular web request.
16
+
-Identifies the median, fastest, and slowest response times for each web request made by your customers.
17
+
- Helps you identify the "hot" code path spending the most time handling a particular web request.
18
18
19
-
Enable the Profiler on all of your Azure applications to catch issues early and prevent your customers from being widely impacted. When you enable the Profiler, it will gather data with these triggers:
19
+
Enable the Profiler on all your Azure applications to catch issues early and prevent your customers from being widely affected. When you enable Profiler, it gathers data with these triggers:
20
20
21
-
-**Sampling Trigger**: starts the Profiler randomly about once an hour for 2 minutes.
22
-
-**CPU Trigger**: starts the Profiler when the CPU usage percentage is over 80%.
23
-
-**Memory Trigger**: starts the Profiler when memory usage is above 80%.
21
+
-**Sampling trigger**: Starts Profiler randomly about once an hour for two minutes.
22
+
-**CPU trigger**: Starts Profiler when the CPU usage percentage is over 80 percent.
23
+
-**Memory trigger**: Starts Profiler when memory usage is above 80 percent.
24
24
25
25
Each of these triggers can be configured, enabled, or disabled on the [Configure Profiler page](./profiler-settings.md#trigger-settings).
26
26
27
27
## Overhead and sampling algorithm
28
28
29
-
Profiler randomly runs two minutes/hour on each virtual machine hosting the application with Profiler enabled for capturing traces. When Profiler is running, it adds from 5-15% CPU overhead to the server.
29
+
Profiler randomly runs two minutes per hour on each virtual machine hosting the application with Profiler enabled for capturing traces. When Profiler is running, it adds from 5 percent to 15 percent CPU overhead to the server.
30
30
31
31
## Supported in Profiler
32
32
33
-
Profiler works with .NET applications deployed on the following Azure services. View specific instructions for enabling Profiler for each service type in the links below.
33
+
Profiler works with .NET applications deployed on the following Azure services. View specific instructions for enabling Profiler for each service type in the following links.
|[Azure Container Instances for Windows](profiler-containers.md)| No | Yes | No |
42
42
|[Azure Container Instances for Linux](profiler-containers.md)| No | Yes | No |
@@ -45,21 +45,21 @@ Profiler works with .NET applications deployed on the following Azure services.
45
45
| Azure Spring Cloud | N/A | No | No |
46
46
|[Azure Service Fabric](profiler-servicefabric.md)| Yes | Yes | No |
47
47
48
-
If you've enabled Profiler but aren't seeing traces, check our[Troubleshooting guide](profiler-troubleshooting.md).
48
+
If you've enabled Profiler but aren't seeing traces, see the[Troubleshooting guide](profiler-troubleshooting.md).
49
49
50
50
## Limitations
51
51
52
-
-**Data retention**: The default data retention period is five days.
53
-
-**Profiling web apps**:
54
-
-While you can use the Profiler at no extra cost, your web app must be hosted in the basic tier of the Web Apps feature of Azure App Service, at minimum.
55
-
- You can only attach 1 profiler to each web app.
52
+
-**Data retention**: The default data retention period is five days.
53
+
-**Profiling web apps**:
54
+
-Although you can use Profiler at no extra cost, your web app must be hosted in the basic tier of the Web Apps feature of Azure App Service, at minimum.
55
+
- You can attach only one profiler to each web app.
56
56
57
57
## Next steps
58
58
Learn how to enable Profiler on your Azure service:
0 commit comments