Merge pull request #200115 from hhunter-ms/hh-1945405

[Profiler] Freshness pass for enabling on Service Fabric

Author: GitHubber17

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

@@ -1,57 +1,77 @@
 ---
-title: Profile live Azure Service Fabric apps with Application Insights
-description: Enable Profiler for a Service Fabric application
+title: Enable Profiler for Azure Service Fabric applications
+description: Profile live Azure Service Fabric apps with Application Insights
 ms.topic: conceptual
 ms.custom: devx-track-dotnet
-ms.date: 08/06/2018
-ms.reviewer: jogrima
+ms.date: 06/23/2022
 ---
 
-# Profile live Azure Service Fabric applications with Application Insights
+# Enable Profiler for Azure Service Fabric applications
 
-You can also deploy Application Insights Profiler on these services:
-* [Azure App Service](profiler.md?toc=/azure/azure-monitor/toc.json)
-* [Azure Cloud Services](profiler-cloudservice.md?toc=/azure/azure-monitor/toc.json)
-* [Azure Virtual Machines](profiler-vm.md?toc=/azure/azure-monitor/toc.json)
+Application Insights Profiler is included with Azure Diagnostics. You can install the Azure Diagnostics extension by using an Azure Resource Manager template for your Service Fabric cluster. Get a [template that installs Azure Diagnostics on a Service Fabric Cluster](https://github.com/Azure/azure-docs-json-samples/blob/master/application-insights/ServiceFabricCluster.json).
 
-## Set up the environment deployment definition
+In this article, you will:
 
-Application Insights Profiler is included with Azure Diagnostics. You can install the Azure Diagnostics extension by using an Azure Resource Manager template for your Service Fabric cluster. Get a [template that installs Azure Diagnostics on a Service Fabric Cluster](https://github.com/Azure/azure-docs-json-samples/blob/master/application-insights/ServiceFabricCluster.json).
+- Add the Application Insights Profiler property to your Azure Resource Manager template.
+- Deploy your Service Fabric cluster with the Application Insights Profiler instrumentation key.
+- Enable Application Insights on your Service Fabric application.
+- Redeploy your Service Fabric cluster to enable Profiler.
+
+## Prerequisites
+
+- Profiler supports .NET Framework, .NET Core, and .NET Core [LTS](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) and newer applications.
+  - Verify you're using [.NET Framework 4.6.1](/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed) or later. 
+  - Confirm that the deployed OS is `Windows Server 2012 R2` or later. 
+- [An Azure Service Fabric managed cluster](../../service-fabric/quickstart-managed-cluster-portal.md).
 
-To set up your environment, take the following actions:
+## Create deployment template
 
-1. Profiler supports .NET Framework and .Net Core. If you're using .NET Framework, make sure you're using [.NET Framework 4.6.1](/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed) or later. It's sufficient to confirm that the deployed OS is `Windows Server 2012 R2` or later. Profiler supports .NET Core [LTS](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) and newer applications.
+1. In your Service Fabric managed cluster, navigate to where you've implemented the [Azure Resource Manager template](https://github.com/Azure/azure-docs-json-samples/blob/master/application-insights/ServiceFabricCluster.json).
 
-1. Search for the [Azure Diagnostics](../agents/diagnostics-extension-overview.md) extension in the deployment template file.
+1. Locate the `WadCfg` tags in the [Azure Diagnostics](../agents/diagnostics-extension-overview.md) extension in the deployment template file.
 
 1. Add the following `SinksConfig` section as a child element of `WadCfg`. Replace the `ApplicationInsightsProfiler` property value with your own Application Insights instrumentation key:  
 
-      ```json
-      "SinksConfig": {
-        "Sink": [
-          {
-            "name": "MyApplicationInsightsProfilerSink",
-            "ApplicationInsightsProfiler": "00000000-0000-0000-0000-000000000000"
-          }
-        ]
-      }
-      ```
+  ```json
+  "settings": {
+      "WadCfg": {
+          "SinksConfig": {
+              "Sink": [
+                  {
+                      "name": "MyApplicationInsightsProfilerSinkVMSS",
+                      "ApplicationInsightsProfiler": "YOUR_APPLICATION_INSIGHTS_INSTRUMENTATION_KEY"
+                  }
+              ]
+          },
+      },
+  }  
+  ```
+
+  For information about adding the Diagnostics extension to your deployment template, see [Use monitoring and diagnostics with a Windows VM and Azure Resource Manager templates](../../virtual-machines/extensions/diagnostics-template.md).
+
+## Deploy your Service Fabric cluster
+
+After updating the `WadCfg` with your instrumentation key, deploy your Service Fabric cluster.  
+  
+Application Insights Profiler will be installed and enabled when the Azure Diagnostics extension is installed. 
+
+## Enable Application Insights on your Service Fabric application
 
-      For information about adding the Diagnostics extension to your deployment template, see [Use monitoring and diagnostics with a Windows VM and Azure Resource Manager templates](../../virtual-machines/extensions/diagnostics-template.md?toc=/azure/virtual-machines/windows/toc.json).
+For Profiler to collect profiles for your requests, your application must be tracking operations with Application Insights. 
 
-1. Deploy your Service Fabric cluster by using your Azure Resource Manager template.  
-  If your settings are correct, Application Insights Profiler will be installed and enabled when the Azure Diagnostics extension is installed. 
+- **For stateless APIs**, you can refer to instructions for [tracking requests for profiling](./profiler-trackrequests.md). 
+- **For tracking custom operations in other kinds of apps**, see [track custom operations with Application Insights .NET SDK](../app/custom-operations-tracking.md).
 
-1. Add Application Insights to your Service Fabric application.  
-  For Profiler to collect profiles for your requests, your application must be tracking operations with Application Insights. For stateless APIs, you can refer to instructions for [tracking Requests for profiling](profiler-trackrequests.md?toc=/azure/azure-monitor/toc.json). For more information about tracking custom operations in other kinds of apps, see [track custom operations with Application Insights .NET SDK](../app/custom-operations-tracking.md).
+Redeploy your application once you've enabled Application Insights.
 
-1. Redeploy your application.
+## Generate traffic and view Profiler traces
 
+1. Launch an [availability test](../app/monitor-web-app-availability.md) to generate traffic to your application. 
+1. Wait 10 to 15 minutes for traces to be sent to the Application Insights instance.
+1. View the [Profiler traces](./profiler-overview.md) via the Application Insights instance the Azure portal.
 
 ## Next steps
 
-* Generate traffic to your application (for example, launch an [availability test](../app/monitor-web-app-availability.md)). Then, wait 10 to 15 minutes for traces to start to be sent to the Application Insights instance.
-* See [Profiler traces](profiler-overview.md?toc=/azure/azure-monitor/toc.json) in the Azure portal.
-* For help with troubleshooting Profiler issues, see [Profiler troubleshooting](profiler-troubleshooting.md?toc=/azure/azure-monitor/toc.json).
+For help with troubleshooting Profiler issues, see [Profiler troubleshooting](./profiler-troubleshooting.md).
 
-[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
+[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]