Merge pull request #207384 from hhunter-ms/hh-1945416

[Profiler] Track requests freshness pass

Author: JamesJBarnett

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

@@ -3,19 +3,19 @@ title: Write code to track requests with Azure Application Insights | Microsoft
 description: Write code to track requests with Application Insights so you can get profiles for your requests.
 ms.topic: conceptual
 ms.custom: devx-track-csharp
-ms.date: 08/06/2018
-ms.reviewer: jogrima
+ms.date: 08/09/2022
+ms.reviewer: charles.weininger
 ---
 
 # Write code to track requests with Application Insights
 
-To view profiles for your application on the Performance page, Azure Application Insights needs to track requests for your application. Application Insights can automatically track requests for applications that are built on already-instrumented frameworks. Two examples are ASP.NET and ASP.NET Core. 
+Azure Application Insights needs to track requests for your application in order to provide profiles for your application on the Performance page in the Azure portal. 
 
-For other applications, such as Azure Cloud Services worker roles and Service Fabric stateless APIs, you need to write code to tell Application Insights where your requests begin and end. After you've written this code, requests telemetry is sent to Application Insights. You can view the telemetry on the Performance page, and profiles are collected for those requests. 
+For applications built on already-instrumented frameworks (like ASP.NET and ASP.NET Core)S, Application Insights can automatically track requests. 
 
-[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+But for other applications (like Azure Cloud Services worker roles and 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. 
 
-To manually track requests, do the following:
+To manually track requests:
 
   1. Early in the application lifetime, add the following code:  
 
@@ -25,6 +25,7 @@ To manually track requests, do the following:
         // Replace with your own Application Insights instrumentation key.
         TelemetryConfiguration.Active.InstrumentationKey = "00000000-0000-0000-0000-000000000000";
         ```
+    
       For more information about this global instrumentation key configuration, see [Use Service Fabric with Application Insights](https://github.com/Azure-Samples/service-fabric-dotnet-getting-started/blob/dev/appinsights/ApplicationInsights.md).  
 
   1. For any piece of code that you want to instrument, add a `StartOperation<RequestTelemetry>` **using** statement around it, as shown in the following example:
@@ -41,7 +42,7 @@ To manually track requests, do the following:
         }
         ```
 
-        Calling `StartOperation<RequestTelemetry>` within another `StartOperation<RequestTelemetry>` scope isn't supported. You can use `StartOperation<DependencyTelemetry>` in the nested scope instead. For example:  
+      Calling `StartOperation<RequestTelemetry>` within another `StartOperation<RequestTelemetry>` scope isn't supported. You can use `StartOperation<DependencyTelemetry>` in the nested scope instead. For example:  
 
         ```csharp
         using (var getDetailsOperation = client.StartOperation<RequestTelemetry>("GetProductDetails"))
@@ -81,3 +82,9 @@ To manually track requests, do the following:
         }
         }
         ```
+
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+
+## Next steps
+
+Troubleshoot the [Application Insights Profiler](./profiler-troubleshooting.md).