Merge pull request #98239 from itechedit/service-bus-diagnostic-logs

edit pass: service-bus-diagnostic-logs

Author: ShawnJackson

articles/service-bus-messaging/service-bus-diagnostic-logs.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Service Bus diagnostic logs | Microsoft Docs
-description: Learn how to set up diagnostic logs for Service Bus in Azure.
+title: Azure Service Bus diagnostics logs | Microsoft Docs
+description: Learn how to set up diagnostics logs for Service Bus in Azure.
 keywords:
 documentationcenter: .net
 services: service-bus-messaging
@@ -18,20 +18,20 @@ ms.date: 01/23/2019
 ms.author: aschhab
 
 ---
-# Enable diagnostic logs for Service Bus
+# Enable diagnostics logs for Service Bus
 
-When you start using your Azure Service Bus namespace, you may want to monitor how and when your namespace is created, deleted or accessed. This article provides an overview of all the operational/diagnostic logs that are available.
+When you start using your Azure Service Bus namespace, you might want to monitor how and when your namespace is created, deleted, or accessed. This article provides an overview of all the operational and diagnostics logs that are available.
 
-Azure Service Bus currently supports activity/operational logs which capture **management operations** performed on the Azure Service Bus namespace. Specifically, these logs capture the operation type, including queue creation, resources used, and the status of the operation.
+Azure Service Bus currently supports activity and operational logs, which capture *management operations* that are performed on the Azure Service Bus namespace. Specifically, these logs capture the operation type, including queue creation, resources used, and the status of the operation.
 
 ## Operational logs schema
 
-All logs are stored in JavaScript Object Notation (JSON) format in the below 2 locations.
+All logs are stored in JavaScript Object Notation (JSON) format in the following two locations:
 
-- **AzureActivity** - displays logs from operations/actions conducted against your namespace on the portal or through Azure Resource Manager template deployments.
-- **AzureDiagnostics** - displays logs from operations/actions conducted against your namespace using the API, or through management clients on the language SDK.
+- **AzureActivity**: Displays logs from operations and actions that are conducted against your namespace in the Azure portal or through Azure Resource Manager template deployments.
+- **AzureDiagnostics**: Displays logs from operations and actions that are conducted against your namespace by using the API, or through management clients on the language SDK.
 
-Operational log JSON strings include elements listed in the following table:
+Operational log JSON strings include the elements listed in the following table:
 
 | Name | Description |
 | ------- | ------- |
@@ -42,7 +42,7 @@ Operational log JSON strings include elements listed in the following table:
 | EventTimeString | Operation time |
 | EventProperties | Operation properties |
 | Status | Operation status |
-| Caller | Caller of operation (Azure portal or management client) |
+| Caller | Caller of operation (the Azure portal or management client) |
 | Category | OperationalLogs |
 
 Here's an example of an operational log JSON string:
@@ -61,14 +61,14 @@ Here's an example of an operational log JSON string:
 }
 ```
 
-## What events/operations are captured in operational logs?
+## Events and operations captured in operational logs
 
-Operation logs capture all management operations performed on the Azure Service Bus namespace. Data operations are not captured because of the high volume of data operations that are conducted on Azure Service Bus.
+Operational logs capture all management operations that are performed on the Azure Service Bus namespace. Data operations are not captured, because of the high volume of data operations that are conducted on Azure Service Bus.
 
 > [!NOTE]
-> To better track data operations, we recommend using client side tracing.
+> To help you better track data operations, we recommend using client-side tracing.
 
-The below management operations are captured in operational logs - 
+The following management operations are captured in operational logs: 
 
 | Scope | Operation|
 |-------| -------- |
@@ -78,40 +78,42 @@ The below management operations are captured in operational logs -
 | Subscription | <ul> <li> Create Subscription </li> <li> Update Subscription </li> <li> Delete Subscription </li> </ul> |
 
 > [!NOTE]
-> Currently, **Read** operations are not tracked in the operational logs.
+> Currently, *Read* operations are not tracked in the operational logs.
 
-## How to enable operational logs?
+## Enable operational logs
 
-Operational logs are disabled by default. To enable diagnostic logs, perform the following steps:
+Operational logs are disabled by default. To enable diagnostics logs, do the following:
 
-1. In the [Azure portal](https://portal.azure.com), navigate to your Azure Service Bus namespace and under **Monitoring**, click **Diagnostics settings**.
+1. In the [Azure portal](https://portal.azure.com), go to your Azure Service Bus namespace and then, under **Monitoring**, select  **Diagnostic settings**.
 
-   ![blade navigation to diagnostic logs](./media/service-bus-diagnostic-logs/image1.png)
+   ![The "Diagnostic settings" link](./media/service-bus-diagnostic-logs/image1.png)
 
-2. Click **Add diagnostic setting** to configure the diagnostic settings.  
+1. In the **Diagnostics settings** pane, select **Add diagnostic setting**.  
 
-   ![turn on diagnostic logs](./media/service-bus-diagnostic-logs/image2.png)
+   ![The "Add diagnostic setting" link](./media/service-bus-diagnostic-logs/image2.png)
 
-3. Configure the diagnostic settings
-   1. Type a **name** to identify the diagnostic settings.
-   2. Pick a destination for the diagnostics.
-      - If you pick **Storage account**, you need to configure the storage account where the diagnostics will be stored.
-      - If you pick **Event hubs**, you need to configure the appropriate Event Hub where the diagnostics settings will be streamed to.
-      - If you pick **Log Analytics**, you need to specify which instance of Log Analytics the diagnostics will be sent.
-    3. Check **OperationalLogs**.
+1. Configure the diagnostics settings by doing the following:
 
-       ![change status diagnostic logs](./media/service-bus-diagnostic-logs/image3.png)
+   a. In the **Name** box, enter a name for the diagnostics settings.  
 
-4. Click **Save**.
+   b. Select one of the following three destinations for your diagnostics logs:  
+   - If you select **Archive to a storage account**, you need to configure the storage account where the diagnostics logs will be stored.  
+   - If you select **Stream to an event hub**, you need to configure the event hub that you want to stream the diagnostics logs to.
+   - If you select **Send to Log Analytics**, you need to specify which instance of Log Analytics the diagnostics will be sent to.  
 
+   c. Select the **OperationalLogs** check box.
 
-New settings take effect in about 10 minutes. After that, logs appear in the configured archival target, on the **Diagnostics logs** blade.
+    ![The "Diagnostics settings" pane](./media/service-bus-diagnostic-logs/image3.png)
 
-For more information about configuring diagnostics, see the [overview of Azure diagnostic logs](../azure-monitor/platform/diagnostic-logs-overview.md).
+1. Select **Save**.
+
+The new settings take effect in about 10 minutes. The logs are displayed in the configured archival target, in the **Diagnostics logs** pane.
+
+For more information about configuring diagnostics settings, see the [overview of Azure diagnostics logs](../azure-monitor/platform/diagnostic-logs-overview.md).
 
 ## Next steps
 
-See the following links to learn more about Service Bus:
+To learn more about Service Bus, see:
 
 * [Introduction to Service Bus](service-bus-messaging-overview.md)
 * [Get started with Service Bus](service-bus-dotnet-get-started-with-queues.md)