Merge pull request #235644 from paulth1/profiler-articles

[AQ] edit pass: Profiler articles

Author: ShawnJackson

articles/azure-monitor/profiler/profiler-overview.md

@@ -1,6 +1,6 @@
 ---
 title: Profile production apps in Azure with Application Insights Profiler
-description: Identify the hot path in your web server code with a low-footprint profiler
+description: Identify the hot path in your web server code with a low-footprint profiler.
 ms.contributor: charles.weininger
 ms.topic: conceptual
 ms.date: 07/15/2022
@@ -9,34 +9,34 @@ ms.reviewer: jogrima
 
 # Profile production applications in Azure with Application Insights Profiler
 
-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.
+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.
 
-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:
+With Application Insights Profiler, you can capture and 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:
 
-- The median, fastest, and slowest response times for each web request made by your customers.
-- Helps you identify the “hot” code path spending the most time handling a particular web request. 
+- Identifies the median, fastest, and slowest response times for each web request made by your customers.
+- Helps you identify the "hot" code path spending the most time handling a particular web request.
 
-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:
+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:
 
-- **Sampling Trigger**: starts the Profiler randomly about once an hour for 2 minutes.
-- **CPU Trigger**: starts the Profiler when the CPU usage percentage is over 80%.
-- **Memory Trigger**: starts the Profiler when memory usage is above 80%.
+- **Sampling trigger**: Starts Profiler randomly about once an hour for two minutes.
+- **CPU trigger**: Starts Profiler when the CPU usage percentage is over 80 percent.
+- **Memory trigger**: Starts Profiler when memory usage is above 80 percent.
 
 Each of these triggers can be configured, enabled, or disabled on the [Configure Profiler page](./profiler-settings.md#trigger-settings).
 
 ## Overhead and sampling algorithm
 
-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.
+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.
 
 ## Supported in Profiler
 
-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.
+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.
 
 | Compute platform | .NET (>= 4.6) | .NET Core | Java |
 | ---------------- | ------------- | --------- | ---- |
 | [Azure App Service](profiler.md) | Yes | Yes | No |
-| [Azure Virtual Machines and virtual machine scale sets for Windows](profiler-vm.md) | Yes | Yes | No |
-| [Azure Virtual Machines and virtual machine scale sets for Linux](profiler-aspnetcore-linux.md) | No | Yes | No |
+| [Azure Virtual Machines and Virtual Machine Scale Sets for Windows](profiler-vm.md) | Yes | Yes | No |
+| [Azure Virtual Machines and Virtual Machine Scale Sets for Linux](profiler-aspnetcore-linux.md) | No | Yes | No |
 | [Azure Cloud Services](profiler-cloudservice.md) | Yes | Yes | N/A |
 | [Azure Container Instances for Windows](profiler-containers.md) | No | Yes | No |
 | [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.
 | Azure Spring Cloud | N/A | No | No |
 | [Azure Service Fabric](profiler-servicefabric.md) | Yes | Yes | No |
 
-If you've enabled Profiler but aren't seeing traces, check our [Troubleshooting guide](profiler-troubleshooting.md).
+If you've enabled Profiler but aren't seeing traces, see the [Troubleshooting guide](profiler-troubleshooting.md).
 
 ## Limitations
 
-- **Data retention**: The default data retention period is five days. 
-- **Profiling web apps**: 
-   - 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.
-   - You can only attach 1 profiler to each web app. 
+- **Data retention**: The default data retention period is five days.
+- **Profiling web apps**:
+   - 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.
+   - You can attach only one profiler to each web app.
 
 ## Next steps
 Learn how to enable Profiler on your Azure service:
 - [Azure App Service](./profiler.md)
 - [Azure Functions app](./profiler-azure-functions.md)
-- [Cloud Service](./profiler-cloudservice.md)
-- [Service Fabric app](./profiler-servicefabric.md)
-- [Azure Virtual Machine](./profiler-vm.md)
+- [Azure Cloud Services](./profiler-cloudservice.md)
+- [Azure Service Fabric app](./profiler-servicefabric.md)
+- [Azure Virtual Machines](./profiler-vm.md)
 - [ASP.NET Core application hosted in Linux on Azure App Service](./profiler-aspnetcore-linux.md)
 - [ASP.NET Core application running in containers](./profiler-containers.md)

articles/azure-monitor/profiler/profiler-settings.md

@@ -1,100 +1,101 @@
 ---
 title: Configure Application Insights Profiler | Microsoft Docs
-description: Use the Azure Application Insights Profiler settings pane to see Profiler status and start profiling sessions
+description: Use the Application Insights Profiler settings pane to see Profiler status and start profiling sessions
 ms.contributor: Charles.Weininger
 ms.topic: conceptual
 ms.date: 08/09/2022
 ---
 
 # Configure Application Insights Profiler
 
-Once you've enabled the Application Insights Profiler, you can:
+After you enable Application Insights Profiler, you can:
 
-- Start a new profiling session
-- Configure Profiler triggers
-- View recent profiling sessions
+- Start a new profiling session.
+- Configure Profiler triggers.
+- View recent profiling sessions.
 
-To open the Azure Application Insights Profiler settings pane, select **Performance** from the pane on the left within your Application Insights page.
+To open the Application Insights Profiler settings pane, select **Performance** on the left pane on your Application Insights page.
 
-:::image type="content" source="./media/profiler-settings/performance-blade-inline.png" alt-text="Screenshot of the link to open performance pane." lightbox="media/profiler-settings/performance-blade.png":::
+:::image type="content" source="./media/profiler-settings/performance-blade-inline.png" alt-text="Screenshot that shows the link to open the Performance pane." lightbox="media/profiler-settings/performance-blade.png":::
 
-View profiler traces across your Azure resources via two methods: 
+You can view Profiler traces across your Azure resources via two methods:
 
-**Profiler button** 
+- By the **Profiler** button:
 
-Select the **Profiler** button from the top menu.
+   Select **Profiler**.
 
-:::image type="content" source="./media/profiler-overview/profiler-button-inline.png" alt-text="Screenshot of the Profiler button from the Performance pane." lightbox="media/profiler-settings/profiler-button.png":::
+  :::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":::
 
-**By operation**
+- By operation:
 
-1. Select an operation from the **Operation name** list ("Overall" is highlighted by default).
-1. Select the **Profiler traces** button.
+   1. Select an operation from the **Operation name** list. **Overall** is highlighted by default.
+   1. Select **Profiler traces**.
 
-   :::image type="content" source="./media/profiler-settings/operation-entry-inline.png" alt-text="Screenshot of selecting operation and Profiler traces to view all profiler traces." lightbox="media/profiler-settings/operation-entry.png":::
+      :::image type="content" source="./media/profiler-settings/operation-entry-inline.png" alt-text="Screenshot that shows selecting operation and Profiler traces to view all Profiler traces." lightbox="media/profiler-settings/operation-entry.png":::
 
-1. Select one of the requests from the list to the left.
-1. Select **Configure Profiler**.
+   1. Select one of the requests from the list on the left.
+   1. Select **Configure Profiler**.
 
-   :::image type="content" source="./media/profiler-settings/configure-profiler-inline.png" alt-text="Screenshot of the overall selection and clicking Profiler traces to view all profiler traces." lightbox="media/profiler-settings/configure-profiler.png":::
+      :::image type="content" source="./media/profiler-settings/configure-profiler-inline.png" alt-text="Screenshot that shows the overall selection and clicking Profiler traces to view all profiler traces." lightbox="media/profiler-settings/configure-profiler.png":::
 
-Once within the Profiler, you can configure and view the Profiler. The **Application Insights Profiler** page has these features:
+Within Profiler, you can configure and view Profiler. The **Application Insights Profiler** page has the following features.
 
-:::image type="content" source="./media/profiler-settings/configure-blade-inline.png" alt-text="Screenshot of profiler page features and settings." lightbox="media/profiler-settings/configure-blade.png":::
+:::image type="content" source="./media/profiler-settings/configure-blade-inline.png" alt-text="Screenshot that shows Profiler page features and settings." lightbox="media/profiler-settings/configure-blade.png":::
 
 | Feature | Description |
 |-|-|
-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, which you can sort using the filters at the top of the page.
+**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 Profiler to run.
+**Recent profiling sessions** | Displays information about past profiling sessions, which you can sort by using the filters at the top of the page.
 
-## Profile Now
-Select **Profile Now** 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.
+## Profile now
+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.
 
-To manually trigger a profiler session, you'll 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'll need the "Application Insights Component Contributor" subscription scope role added. [See more about role access control with Azure Monitoring](../app/resources-roles-access-control.md).
+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).
 
-## Trigger Settings
+## Trigger settings
 
-Select the Triggers button on the menu bar to open the CPU, Memory, and Sampling trigger settings pane. 
+Select **Triggers** to open the **Trigger Settings** pane that has the **CPU**, **Memory**, and **Sampling** trigger tabs.
 
-**CPU or Memory triggers**
+### CPU or Memory triggers
 
-You can set up a trigger to start profiling when the percentage of CPU or Memory use hits the level you set.
+You can set up a trigger to start profiling when the percentage of CPU or memory use hits the level you set.
 
-:::image type="content" source="./media/profiler-settings/cpu-memory-trigger-settings.png" alt-text="Screenshot of trigger settings pane for C P U and Memory triggers.":::
+:::image type="content" source="./media/profiler-settings/cpu-memory-trigger-settings.png" alt-text="Screenshot that shows the Trigger Settings pane for C P U and Memory triggers.":::
 
 | Setting | Description |
 |-|-|
-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.
+On/Off button | On: Starts Profiler. Off: Doesn't start Profiler.
+Memory threshold | When this percentage of memory is in use, Profiler is started.
+Duration | Sets the length of time Profiler runs when triggered.
+Cooldown | Sets the length of time Profiler waits before checking for the memory or CPU usage again after it's triggered.
 
-**Sampling trigger**
+### Sampling trigger
 
-Unlike CPU or memory triggers, the Sampling trigger isn't triggered by an event. Instead, it's triggered randomly to get a truly random sample of your application's performance. You can:
+Unlike CPU or Memory triggers, an event doesn't trigger the Sampling trigger. Instead, it's triggered randomly to get a truly random sample of your application's performance.
+You can:
 - Turn this trigger off to disable random sampling.
-- Set how often profiling will occur and the duration of the profiling session. 
+- Set how often profiling occurs and the duration of the profiling session.
 
-:::image type="content" source="./media/profiler-settings/sampling-trigger-settings.png" alt-text="Screenshot of trigger settings pane for Sampling trigger.":::
+:::image type="content" source="./media/profiler-settings/sampling-trigger-settings.png" alt-text="Screenshot that shows the Trigger Settings pane for Sampling trigger.":::
 
 | Setting | Description |
 |-|-|
-On / Off Button | On: profiler can be started by this trigger; Off: profiler won't be started by this trigger.
-Sample rate | The rate at which the profiler can occur. </br> <ul><li>The **Normal** setting collects data 5% of the time, which is about 2 minutes per hour.</li><li>The **High** setting profiles 50% of the time.</li><li>The **Maximum** setting profiles 75% of the time.</li></ul> </br> Normal is recommended for production environments.
-Duration | Sets the length of time the profiler will run when triggered.
+On/Off button | On: Starts Profiler. Off: Doesn't start Profiler.
+Sample rate | The rate at which Profiler can occur. </br> <ul><li>The **Normal** setting collects data 5% of the time, which is about 2 minutes per hour.</li><li>The **High** setting profiles 50% of the time.</li><li>The **Maximum** setting profiles 75% of the time.</li></ul> </br> We recommend the **Normal** setting for production environments.
+Duration | Sets the length of time Profiler runs when triggered.
 
-## Recent Profiling Sessions
-This section of the Profiler page displays recent profiling session information. A profiling session represents the time taken by the profiler agent while profiling one of the machines hosting your application. Open the profiles from a session by clicking on one of the rows. For each session, we show:
+## Recent profiling sessions
+This section of the **Profiler** page displays recent profiling session information. A profiling session represents the time taken by the Profiler agent while profiling one of the machines that hosts your application. Open the profiles from a session by selecting one of the rows. For each session, we show the following settings.
 
 | Setting | Description |
 |-|-|
-Triggered by | How the session was started, either by a trigger, Profile Now, or default sampling. 
+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.
+Machine Instance | Name of the machine the Profiler agent ran on.
 Timestamp | Time when the profile was captured.
-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.
+CPU % | Percentage of CPU used while Profiler was running.
+Memory % | Percentage of memory used while Profiler was running.
 
 ## Next steps
 [Enable Profiler and view traces](profiler-overview.md?toc=/azure/azure-monitor/toc.json)