Event Hubs diagnostic logs

Author: spelluru

articles/event-hubs/event-hubs-diagnostic-logs.md

@@ -15,54 +15,52 @@ ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: data-services
 ms.custom: seodec18
-ms.date: 12/06/2018
+ms.date: 04/28/2020
 ms.author: shvija
 
 ---
 # Set up diagnostic logs for an Azure event hub
 
 You can view two types of logs for Azure Event Hubs:
 
-* **[Activity logs](../azure-monitor/platform/platform-logs-overview.md)**: These logs have information about operations performed on a job. The logs are always enabled.
+* **[Activity logs](../azure-monitor/platform/platform-logs-overview.md)**: These logs have information about operations performed on a job. The logs are always enabled. You can see activity log entries by selecting **Activity log** on the left menu for your event hub namespace in the Azure portal. For example: "Create or Update Namespace", "Create or Update Event Hub".
+
+    ![Activity log for an Event Hubs namespace](./media/event-hubs-diagnostic-logs/activity-log.png)
 * **[Diagnostic logs](../azure-monitor/platform/platform-logs-overview.md)**: You can configure diagnostic logs for a richer view of everything that happens with a job. Diagnostic logs cover activities from the time the job is created until the job is deleted, including updates and activities that occur while the job is running.
 
+    The following section shows you how to enable diagnostic logs for an Event Hubs namespace.
 
 ## Enable diagnostic logs
-
 Diagnostic logs are disabled by default. To enable diagnostic logs, follow these steps:
 
-1.	In the [Azure portal](https://portal.azure.com), under **Monitoring + Management**, click **Diagnostics logs**.
-
-    ![Pane navigation to diagnostic logs](./media/event-hubs-diagnostic-logs/image1.png)
-
-2.	Click the resource you want to monitor.
-
-3.	Click **Turn on diagnostics**.
-
-	![Turn on diagnostic logs](./media/event-hubs-diagnostic-logs/image2.png)
-
-4.	For **Status**, click **On**.
-
-	![Change the status of diagnostic logs](./media/event-hubs-diagnostic-logs/image3.png)
+1.	In the [Azure portal](https://portal.azure.com), navigate to your Event Hubs namespace. 
+2. Select **Diagnostics settings** under **Monitoring** in the left pane, and then select **+ Add diagnostic setting**. 
 
-5.	Set the archive target that you want; for example, a storage account, an event hub, or Azure Monitor logs.
+    ![Diagnostic settings page - add diagnostic setting](./media/event-hubs-diagnostic-logs/diagnostic-settings-page.png)
+4. In the **Category details** section, select the **types of diagnostic logs** that you want to enable. You will find details about these categories later in this article. 
+5. In the **Destination details** section, set the archive target (destination) that you want; for example, a storage account, an event hub, or a Log Analytics workspace.
 
-6.	Save the new diagnostics settings.
+    ![Add diagnostic settings page](./media/event-hubs-diagnostic-logs/aDD-diagnostic-settings-page.png)
+6.	Select **Save** on the toolbar to save the diagnostics settings.
 
-New settings take effect in about 10 minutes. After that, logs appear in the configured archival target, in the **Diagnostics logs** pane.
+    New settings take effect in about 10 minutes. After that, logs appear in the configured archival target, in the **Diagnostics logs** pane.
 
-For more information about configuring diagnostics, see the [overview of Azure diagnostic logs](../azure-monitor/platform/platform-logs-overview.md).
+    For more information about configuring diagnostics, see the [overview of Azure diagnostic logs](../azure-monitor/platform/platform-logs-overview.md).
 
 ## Diagnostic logs categories
 
-Event Hubs captures diagnostic logs for two categories:
+Event Hubs captures diagnostic logs for the following categories:
 
-* **Archive Logs**: logs related to Event Hubs archives, specifically, logs related to archive errors.
-* **Operational Logs**: information about what is happening during Event Hubs operations, specifically, the operation type, including event hub creation, resources used, and the status of the operation.
+- **Archive Logs**: logs related to Event Hubs archives, specifically, logs related to archive errors.
+- **Operational Logs**: information about what is happening during Event Hubs operations, specifically, the operation type, including event hub creation, resources used, and the status of the operation.
+- **Auto scale logs**: information about auto-scaling operations done on an Event Hubs namespace. 
+- **Kafka coordinator logs** - information about Kafka coordinator operations related to Event Hubs. 
+- **Kafka user logs**: information about Kafka user operations related to Event Hubs. 
+- **Event Hubs virtual network (VNet) connection event**: information about Event Hubs virtual network connection events. 
+- **Customer managed key user logs**: information about operations related to customer-managed key. 
 
-## Diagnostic logs schema
 
-All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
+    All logs are stored in JavaScript Object Notation (JSON) format. Each entry has string fields that use the format described in the following sections.
 
 ## Archive logs schema