freshness pt 1

Signed-off-by: Hannah Hunter <[email protected]>

Author: hhunter-ms

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

@@ -1,32 +1,32 @@
 ---
-title: Profile production apps in Azure with Application Insights Profiler
+title: Analyze application performance traces with Application Insights 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
-ms.reviewer: jogrima
+ms.date: 09/21/2023
+ms.reviewer: ryankahng
 ---
 
 # Profile production applications in Azure with Application Insights Profiler
 
-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.
+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. 
 
-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:
+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:
 
-- 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.
+- The median, fastest, and slowest response times for each web request made by your customers.
+- The "hot" code path spending the most time handling a particular web request.
 
-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:
+Enable the Profiler on all your Azure applications to gather data with the following triggers:
 
 - **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).
+Each of these triggers can be [configured, enabled, or disabled](./profiler-settings.md#trigger-settings).
 
 ## Overhead and sampling algorithm
 
-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.
+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.
 
 ## Supported in Profiler
 
@@ -42,7 +42,6 @@ Profiler works with .NET applications deployed on the following Azure services.
 | [Azure Container Instances for Linux](profiler-containers.md) | No | Yes | No |
 | Kubernetes | No | Yes | No |
 | [Azure Functions](./profiler-azure-functions.md) | Yes | Yes | No |
-| 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, see the [Troubleshooting guide](profiler-troubleshooting.md).

articles/azure-monitor/profiler/profiler.md

@@ -2,28 +2,25 @@
 title: Enable Profiler for Azure App Service apps | Microsoft Docs
 description: Profile live apps on Azure App Service with Application Insights Profiler.
 ms.topic: conceptual
-ms.date: 05/01/2023
-ms.reviewer: jogrima
+ms.date: 09/21/2023
+ms.reviewer: ryankahng
 ---
 
 # Enable Profiler for Azure App Service apps
 
-Application Insights Profiler is preinstalled as part of the Azure App Service runtime. You can run Profiler on ASP.NET and ASP.NET Core apps running on App Service by using the Basic service tier or higher. Follow these steps even if you've included the Application Insights SDK in your application at build time.
+Application Insights Profiler is preinstalled as part of the Azure App Service runtime. You can run Profiler on ASP.NET and ASP.NET Core apps running on App Service by using the Basic service tier or higher. Follow these steps, even if you included the Application Insights SDK in your application at build time.
 
 To enable Profiler on Linux, walk through the [ASP.NET Core Azure Linux web apps instructions](profiler-aspnetcore-linux.md).
 
 > [!NOTE]
-> Codeless installation of Application Insights Profiler follows the .NET Core support policy.
-> For more information about supported runtime, see [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
+> Codeless installation of Application Insights Profiler follows the .NET Core support policy. For more information about supported runtime, see [.NET Core Support Policy](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
 
 ## Prerequisites
 
-You need:
-
 - An [Azure App Service ASP.NET/ASP.NET Core app](../../app-service/quickstart-dotnetcore.md).
 - An [Application Insights resource](/previous-versions/azure/azure-monitor/app/create-new-resource) connected to your App Service app.
 
-## Verify the Always on setting is enabled
+## Verify the "Always on" setting is enabled
 
 1. In the Azure portal, go to your App Service instance.
 1. Under **Settings** on the left pane, select **Configuration**.