Merge pull request #185518 from msjasteppe/iot-logging-updates

Updating article and adding back to IoT TOC

Author: jborsecnik

articles/healthcare-apis/events/media/events-message-structure/events-overview.png

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: tutorial 
-ms.date: 12/14/2021
+ms.date: 1/20/2022
 ms.author: jasteppe
 ---
 
@@ -34,11 +34,11 @@ Below is a diagram of the IoT device message flow from IoT Hub into IoT connecto
 
 ##  Create a managed identity for IoT Hub
 
-For this tutorial, we'll be using an IoT Hub with a [user-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md).
+For this tutorial, we'll be using an IoT Hub with a [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) to provide access from the IoT Hub to the IoT connector device message event hub.
 
-The user-assigned managed identity will be used to provide access to your IoT connector device message event hub using [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md). 
+For more information about how to create a system-assigned managed identity with your IoT Hub, see [IoT Hub support for managed identities](../../iot-hub/iot-hub-managed-identity.md#system-assigned-managed-identity). 
 
-Follow these directions to create a user-assigned managed identity with your IoT Hub: [IoT Hub support for managed identities](../../iot-hub/iot-hub-managed-identity.md#user-assigned-managed-identity). 
+For more information on Azure role-based access control, see [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md).
 
 ## Connect IoT Hub with IoT connector
 

articles/healthcare-apis/events/media/events-overview/events-overview.png

@@ -1,56 +1,71 @@
 ---
-title: Export IoT connector Metrics through Diagnostic settings - Azure Healthcare APIs
-description: This article explains how to export IoT connector metrics through Diagnostic settings
+title: Configure IoT connector Diagnostic settings for metrics export - Azure Healthcare APIs
+description: This article explains how to configure IoT connector Diagnostic settings for metrics exporting.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: how-to
-ms.date: 11/10/2021
+ms.date: 1/20/2021
 ms.author: jasteppe
 ---
 
-# Export IoT connector Metrics through Diagnostic settings
+# Configure diagnostic setting for IoT connector metrics exporting
 
 > [!IMPORTANT]
 > Azure Healthcare APIs is currently in PREVIEW. The [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
-In this article, you'll learn how to export IoT connector Metrics logs. The feature that enables Metrics logging is the [**Diagnostic settings**](../../azure-monitor/essentials/diagnostic-settings.md) in the Azure portal. 
+In this article, you'll learn how to configure the diagnostic setting for IoT connector to export metrics to different destinations for audit, analysis, or backup.
 
-## Enable Metrics logging for IoT connector
-1. To enable Metrics logging for the IoT connector, select your Fast Healthcare Interoperability Resources (FHIR®) service in the Azure portal. 
+## Create diagnostic setting for IoT connector
+1. To enable metrics export for IoT connector, select **IoT connectors** in your Workspace.
+ 
+   :::image type="content" source="media/iot-metrics-export/iot-connector-logging-workspace.png" alt-text="Screenshot of select IoT connector within Workspace." lightbox="media/iot-metrics-export/iot-connector-logging-workspace.png":::
+
+2. Select the IoT connector that you want to configure metrics export for.
+   
+   :::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-connector.png" alt-text="Screenshot of select IoT connector for exporting metrics" lightbox="media/iot-metrics-export/iot-connector-logging-select-connector.png":::
+
+3. Select the **Diagnostic settings** button and then select the **+ Add diagnostic setting** button.
 
-2. Navigate to **Diagnostic settings** 
+   :::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-diagnostic-settings.png" alt-text="Screenshot of select the Diagnostic settings and select the + Add diagnostic setting buttons." lightbox="media/iot-metrics-export/iot-connector-logging-select-diagnostic-settings.png"::: 
 
-3. Select **+ Add diagnostic setting**
+4. After the **+ Add diagnostic setting** page opens, enter a name in the **Diagnostic setting name** dialog box.   
 
-   :::image type="content" source="media/iot-metrics-export/diagnostic-settings-main.png" alt-text="IoT connector1" lightbox="media/iot-metrics-export/diagnostic-settings-main.png"::: 
+    :::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-diagnostic-configuration.png" alt-text="Screenshot diagnostic setting and required fields." lightbox="media/iot-metrics-export/iot-connector-logging-select-diagnostic-configuration.png"::: 
 
-4. Enter a name in the **Diagnostic setting name** dialog box.
+5. Under **Destination details**, select the destination you want to use to export your IoT connector metrics to. In the above example, we've selected an Azure storage account.
 
-5. Select the method you want to use to access your diagnostic logs:
+   Metrics can be exported to the following destinations:
 
-    1. **Archive to a storage account** for auditing or manual inspection. The storage account you want to use needs to be already created.
-    2. **Stream to Event Hub** for ingestion by a third-party service or custom analytic solution. You'll need to create an Event Hub namespace and Event Hub policy before you can configure this step.
-    3. **Stream to the Log Analytics** workspace in Azure Monitor. You'll need to create your Logs Analytics Workspace before you can select this option.
+   |Destination|Description|
+   |-----------|-----------|
+   |Log Analytics workspace|Metrics are converted to log form. This option may not be available for all resource types. Sending them to the Azure Monitor Logs store (which is searchable via Log Analytics) helps you to integrate them into queries, alerts, and visualizations with existing log data.|
+   |Azure storage account|Archiving logs and metrics to an Azure storage account is useful for audit, static analysis, or backup. Compared to Azure Monitor Logs and a Log Analytics workspace, Azure storage is less expensive and logs can be kept there indefinitely.|
+   |Event Hubs|Sending logs and metrics to Event Hubs allows you to stream data to external systems such as third-party SIEMs and other Log Analytics solutions.|
+   |Azure Monitor partner integrations|Specialized integrations between Azure Monitor and other non-Microsoft monitoring platforms. Useful when you're already using one of the partners.|
+   
+   > [!Important]
+   > Each **Destination details** selection requires that certain resources (for example, an existing Azure storage account) be created and available before the selection can be successfully configured. Choose each selection to get a list of the required resources.
 
-6. Select **Errors, Traffic, and Latency** for IoT connector.  Select any extra metric categories you want to capture for the FHIR service.
+6. Select **AllMetrics**.
 
-7. Select **Save**
+   > [!Note]
+   > To view a complete list of IoT connector metrics associated with **AllMetrics**, see [Supported metrics with Azure Monitor](/azure/azure-monitor/essentials/metrics-supported#microsofthealthcareapisworkspacesiotconnectors). 
 
-   :::image type="content" source="media/iot-metrics-export/diagnostic-setting-add.png" alt-text="IoT connector2" lightbox="media/iot-metrics-export/diagnostic-setting-add.png":::
+7. Select **Save**.
 
-> [!Note] 
-> It might take up to 15 minutes for the first Metrics logs to display in the repository of your choice.  
+   > [!Note] 
+   > It might take up to 15 minutes for the first IoT connector metrics to display in the destination of your choice.  
  
-For more information about how to work with diagnostic logs, see the [Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md)
+For more information about how to work with diagnostics logs, see the [Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md).
 
 ## Conclusion 
-Having access to Metrics logs is essential for monitoring and troubleshooting.  IoT connector allows you to do these actions through Metrics logs. 
+Having access to metrics is essential for monitoring and troubleshooting.  IoT connector allows you to do these actions through the export of metrics. 
 
 ## Next steps
 
-Check out frequently asked questions about IoT connector.
+To view the frequently asked questions (FAQs) about IoT connector, see
 
 >[!div class="nextstepaction"]
 >[IoT connector FAQs](iot-connector-faqs.md)