Merge pull request #31757 from ShawnJackson/service-fabric-diagnostics-how-to-setup

edit pass: service-fabric-diagnostics-how-to-setup articles

Author: KatieCumming

articles/service-fabric/service-fabric-diagnostics-how-to-setup-lad.md

@@ -1,5 +1,5 @@
 <properties
-   pageTitle="How to collect logs with Linux Azure Diagnostics | Microsoft Azure"
+   pageTitle="Collect logs by using Linux Azure Diagnostics | Microsoft Azure"
    description="This article describes how to set up Azure Diagnostics to collect logs from a Service Fabric Linux cluster running in Azure."
    services="service-fabric"
    documentationCenter=".net"
@@ -17,35 +17,32 @@
    ms.author="subramar"/>
 
 
-# How to collect logs with Azure Diagnostics
+# Collect logs by using Azure Diagnostics
 
 > [AZURE.SELECTOR]
 - [Windows](service-fabric-diagnostics-how-to-setup-wad.md)
 - [Linux](service-fabric-diagnostics-how-to-setup-lad.md)
 
-When you're running an Azure Service Fabric cluster, it's a good idea to collect the logs from all the nodes in a central location. Having the logs in a central location makes it easy to analyze and troubleshoot issues, whether they are in your services, application or the cluster itself. One way to upload and collect logs is to use the Azure Diagnostics extension, which uploads logs to Azure Storage. You can read the events from storage and place them into a product such as [Elastic Search](service-fabric-diagnostic-how-to-use-elasticsearch.md) or another log parsing solution.
+When you're running an Azure Service Fabric cluster, it's a good idea to collect the logs from all the nodes in a central location. Having the logs in a central location makes it easy to analyze and troubleshoot issues, whether they are in your services, your application, or the cluster itself. One way to upload and collect logs is to use the Azure Diagnostics extension, which uploads logs to Azure Storage. You can read the events from storage and place them in a product such as [Elastic Search](service-fabric-diagnostic-how-to-use-elasticsearch.md) or another log-parsing solution.
 
-## Different log sources that you may want to collect
-1. **Service Fabric logs:** Emitted by the platform using LTTng and uploaded to your storage account. Logs may be operational events or runtime events emitted by the platform. These logs are stored in the location pointed in your cluster manifest (Search for the tag "AzureTableWinFabETWQueryable", and look for the "StoreConnectionString" to get the storage account details. 
-2. **Application events:** Events emitted from your services code.  You can use any logging solution that writes text-based logfiles, for example [LTTng](http://lttng.org). Refer to th LTTng documentation on tracing your application.  
+## Log sources that you might want to collect
+- **Service Fabric logs**: Emitted from the platform via [LTTng](http://lttng.org) and uploaded to your storage account. Logs can be operational events or runtime events that the platform emits. These logs are stored in the location that the cluster manifest specifies. (To get the storage account details, search for the tag **AzureTableWinFabETWQueryable** and look for **StoreConnectionString**.)
+- **Application events**: Emitted from your service's code. You can use any logging solution that writes text-based log files--for example, LTTng. For more information, see the LTTng documentation on tracing your application.  
 
 
-## Deploy the diagnostics extensions
-The first step in collecting logs is to deploy the Diagnostics extension on each of the VMs in the Service Fabric cluster. The Diagnostics extension collects logs on each VM and uploads them to the storage account you specify. The steps vary based on whether you use the Azure portal or the Azure Resource Manager. 
+## Deploy the Diagnostics extension
+The first step in collecting logs is to deploy the Diagnostics extension on each of the VMs in the Service Fabric cluster. The Diagnostics extension collects logs on each VM and uploads them to the storage account that you specify. The steps vary based on whether you use the Azure portal or Azure Resource Manager.
 
-### Deploy the diagnostics extension as part of cluster creation 
-To deploy diagnostics extension to the VMs in the cluster as part of cluster creation, set "Diagnostics" to **On**. After the cluster has been created, this setting cannot be changed using the portal. 
+To deploy the Diagnostics extension to the VMs in the cluster as part of cluster creation, set **Diagnostics** to **On**. After you create the cluster, you can't change this setting by using the portal.
 
-Configure Linux Azure Diagnostics (LAD) to collect the files and place them into the customers storage account. This process is explained as scenario 3("Upload your own log files") in the article [Using LAD to monitor and diagnose Linux VMs](../virtual-machines/virtual-machines-linux-classic-diagnostic-extension.md). Following this process gets you access to the traces, which can be uploaded to a visualizer of your choice.
+Then, configure Linux Azure Diagnostics (LAD) to collect the files and place them into your storage account. This process is explained as scenario 3 ("Upload your own log files") in the article [Using LAD to monitor and diagnose Linux VMs](../virtual-machines/virtual-machines-linux-classic-diagnostic-extension.md). Following this process gets you access to the traces. You can upload the traces to a visualizer of your choice.
 
+You can also deploy the Diagnostics extension by using Azure Resource Manager. The process is similar for Windows and Linux and is documented for Windows clusters in [How to collect logs with Azure Diagnostics](service-fabric-diagnostics-how-to-setup-wad.md).
 
-You can also deploy the diagnostics extension using the Azure Resource Manager. The process is similar for Windows and Linux and is documented for Windows clusters at [How to collect logs with Azure Diagnostics](service-fabric-diagnostics-how-to-setup-wad.md).
+You can also use Operations Management Suite, as described in [Operations Management Suite Log Analytics with Linux](https://blogs.technet.microsoft.com/hybridcloud/2016/01/28/operations-management-suite-log-analytics-with-linux/).
 
-You can also use OMS as described in [OMS log analytics with linux](https://blogs.technet.microsoft.com/hybridcloud/2016/01/28/operations-management-suite-log-analytics-with-linux/).
-
-After this configuration is done, the LAD agent monitors the log files specified.  Whenever a new line is appended to the file, it creates a syslog entry that is sent to the storage specified by the customer.
+After you finish this configuration, the LAD agent monitors the specified log files. Whenever a new line is appended to the file, it creates a syslog entry that is sent to the storage that you specified.
 
 
 ## Next steps
-Check out [LTTng documentation](http://lttng.org/docs) and [Using LAD](../virtual-machines/virtual-machines-linux-classic-diagnostic-extension.md) to understand in more detail what events you should look into while troubleshooting issues.
-
+To understand in more detail what events you should examine while troubleshooting issues, see [LTTng documentation](http://lttng.org/docs) and [Using LAD](../virtual-machines/virtual-machines-linux-classic-diagnostic-extension.md).