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
Copy file name to clipboardExpand all lines: articles/azure-monitor/profiler/profiler-overview.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,32 +1,32 @@
1
1
---
2
-
title: Profile production apps in Azure with Application Insights Profiler
2
+
title: Analyze application performance traces with Application Insights Profiler
3
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
-
ms.date: 07/15/2022
7
-
ms.reviewer: jogrima
6
+
ms.date: 09/21/2023
7
+
ms.reviewer: ryankahng
8
8
---
9
9
10
10
# Profile production applications in Azure with Application Insights Profiler
11
11
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.
12
+
Diagnosing your application's performance issues can be difficult, especially when running on a production environment in the dynamic cloud. 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 captureand view performance traces for your application in all these dynamic situations. The process occurs automatically at scale 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:
14
+
With Application Insights Profiler, you can capture, identify, and view performance traces for your application running in Azure, regardless of the scenario. The Profiler trace process occurs automatically, at scale, and doesn't negatively affect your users. The Profiler identifies:
15
15
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.
16
+
-The median, fastest, and slowest response times for each web request made by your customers.
17
+
-The "hot" code path spending the most time handling a particular web request.
18
18
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:
19
+
Enable the Profiler on all your Azure applications to gather data with the following triggers:
20
20
21
21
-**Sampling trigger**: Starts Profiler randomly about once an hour for two minutes.
22
22
-**CPU trigger**: Starts Profiler when the CPU usage percentage is over 80 percent.
23
23
-**Memory trigger**: Starts Profiler when memory usage is above 80 percent.
24
24
25
-
Each of these triggers can be configured, enabled, or disabled on the [Configure Profiler page](./profiler-settings.md#trigger-settings).
25
+
Each of these triggers can be [configured, enabled, or disabled](./profiler-settings.md#trigger-settings).
26
26
27
27
## Overhead and sampling algorithm
28
28
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.
29
+
Profiler randomly runs two minutes per hour on each virtual machine hosting applications with Profiler enabled. 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
@@ -42,7 +42,6 @@ Profiler works with .NET applications deployed on the following Azure services.
42
42
|[Azure Container Instances for Linux](profiler-containers.md)| No | Yes | No |
43
43
| Kubernetes | No | Yes | No |
44
44
|[Azure Functions](./profiler-azure-functions.md)| Yes | Yes | No |
45
-
| Azure Spring Cloud | N/A | No | No |
46
45
|[Azure Service Fabric](profiler-servicefabric.md)| Yes | Yes | No |
47
46
48
47
If you've enabled Profiler but aren't seeing traces, see the [Troubleshooting guide](profiler-troubleshooting.md).
description: Use the Application Insights Profiler settings pane to see Profiler status and start profiling sessions
4
4
ms.contributor: Charles.Weininger
5
5
ms.topic: conceptual
6
-
ms.date: 08/09/2022
6
+
ms.date: 09/22/2023
7
7
---
8
8
9
9
# Configure Application Insights Profiler
@@ -20,13 +20,13 @@ To open the Application Insights Profiler settings pane, select **Performance**
20
20
21
21
You can view Profiler traces across your Azure resources via two methods:
22
22
23
-
-By the**Profiler** button:
23
+
-The**Profiler** button:
24
24
25
25
Select **Profiler**.
26
26
27
27
:::image type="content" source="./media/profiler-overview/profiler-button-inline.png" alt-text="Screenshot that shows the Profiler button on the Performance pane." lightbox="media/profiler-settings/profiler-button.png":::
28
28
29
-
-By operation:
29
+
-Operations:
30
30
31
31
1. Select an operation from the **Operation name** list. **Overall** is highlighted by default.
32
32
1. Select **Profiler traces**.
@@ -49,6 +49,7 @@ Within Profiler, you can configure and view Profiler. The **Application Insights
49
49
**Recent profiling sessions** | Displays information about past profiling sessions, which you can sort by using the filters at the top of the page.
50
50
51
51
## Profile now
52
+
52
53
Select **Profile now** to start a profiling session on demand. When you select this link, all Profiler agents that are sending data to this Application Insights instance start to capture a profile. After 5 to 10 minutes, the profile session is shown in the list.
53
54
54
55
To manually trigger a Profiler session, you need, at minimum, *write* access on your role for the Application Insights component. In most cases, you get write access automatically. If you're having issues, you need the **Application Insights Component Contributor** subscription scope role added. For more information, see [Resources, roles, and access control in Application Insights](../app/resources-roles-access-control.md).
@@ -98,6 +99,7 @@ CPU % | Percentage of CPU used while Profiler was running.
98
99
Memory % | Percentage of memory used while Profiler was running.
99
100
100
101
## Next steps
102
+
101
103
[Enable Profiler and view traces](profiler-overview.md?toc=/azure/azure-monitor/toc.json)
Copy file name to clipboardExpand all lines: articles/azure-monitor/profiler/profiler-trackrequests.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,15 +3,13 @@ title: Write code to track requests with Application Insights | Microsoft Docs
3
3
description: Write code to track requests with Application Insights so you can get profiles for your requests.
4
4
ms.topic: conceptual
5
5
ms.custom: devx-track-csharp
6
-
ms.date: 08/09/2022
6
+
ms.date: 09/22/2023
7
7
ms.reviewer: charles.weininger
8
8
---
9
9
10
10
# Write code to track requests with Application Insights
11
11
12
-
Application Insights needs to track requests for your application to provide profiles for your application on the **Performance** page in the Azure portal.
13
-
14
-
For applications built on already-instrumented frameworks (like ASP.NET and ASP.NET Core), Application Insights can automatically track requests.
12
+
Application Insights needs to track requests for your application to provide profiles for your application on the **Performance** page in the Azure portal. For applications built on already-instrumented frameworks (like ASP.NET and ASP.NET Core), Application Insights can automatically track requests.
15
13
16
14
For other applications (like Azure Cloud Services worker roles and Azure Service Fabric stateless APIs), you need to track requests with code that tells Application Insights where your requests begin and end. Requests telemetry is then sent to Application Insights, which you can view on the **Performance** page. Profiles are collected for those requests.
0 commit comments