You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/device-data-through-iot-hub.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: msjasteppe
6
6
ms.service: healthcare-apis
7
7
ms.subservice: iomt
8
8
ms.topic: tutorial
9
-
ms.date: 1/19/2022
9
+
ms.date: 1/20/2022
10
10
ms.author: jasteppe
11
11
---
12
12
@@ -34,11 +34,11 @@ Below is a diagram of the IoT device message flow from IoT Hub into IoT connecto
34
34
35
35
## Create a managed identity for IoT Hub
36
36
37
-
For this tutorial, we'll be using an IoT Hub with a [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md).
37
+
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.
38
38
39
-
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).
39
+
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).
40
40
41
-
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).
41
+
For more information on Azure role-based access control, see [Azure role-based access control (Azure RBAC)](../../role-based-access-control/overview.md).
description: This article explains how to configure IoT connector Diagnostic settings
4
4
services: healthcare-apis
5
5
author: msjasteppe
6
6
ms.service: healthcare-apis
7
7
ms.subservice: iomt
8
8
ms.topic: how-to
9
-
ms.date: 1/19/2021
9
+
ms.date: 1/20/2021
10
10
ms.author: jasteppe
11
11
---
12
12
13
-
# Enable IoT connector diagnostics logging through Diagnostic settings
13
+
# Configure IoT connector Diagnostic settings for metrics export
14
14
15
15
> [!IMPORTANT]
16
16
> 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.
17
17
18
-
In this article, you'll learn how to enable IoT connector diagnostics logging.
18
+
In this article, you'll learn how to configure the Diagnostics settings for IoT connector to export metrics to different destinations for audit, analysis, or backup.
19
19
20
-
## Enable diagnostics logging for IoT connector
21
-
1. To enable diagnostics logging for IoT connector, select **IoT connector** in your Workspace.
20
+
## Create Diagnostic settings exporting your IoT connector metrics
21
+
1. To enable diagnostics metrics export for IoT connector, select **IoT connectors** in your Workspace.
22
22
23
23
:::image type="content" source="media/iot-metrics-export/iot-connector-logging-workspace.png" alt-text="Select IoT connector within Workspace" lightbox="media/iot-metrics-export/iot-connector-logging-workspace.png":::
24
24
25
-
2. Select the IoT connector that you want to enable diagnostics logging for.
25
+
2. Select the IoT connector that you want to configure diagnostics metrics export for.
3. Select the **Diagnostic settings** button and then select the **+ Add diagnostic setting** button.
30
30
31
31
:::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-diagnostic-settings.png" alt-text="Select the Diagnostic settings and select the + Add diagnostic setting buttons." lightbox="media/iot-metrics-export/iot-connector-logging-select-diagnostic-settings.png":::
32
32
33
-
4.The **Diagnostic setting** page will open.
33
+
4.After the **Diagnostic setting** page opens, enter a name in the **Diagnostic setting name** dialog box.
34
34
35
-
:::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-diagnostic-configuration.png" alt-text="Provide a name for your logs, where you want the logs to be sent, ALLMetrics, and save" lightbox="media/iot-metrics-export/iot-connector-logging-select-diagnostic-configuration.png":::
35
+
:::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-diagnostic-configuration.png" alt-text="Provide a name for your diagnostics export, where you want the metrics to be sent, ALLMetrics, and save" lightbox="media/iot-metrics-export/iot-connector-logging-select-diagnostic-configuration.png":::
36
36
37
-
5.Enter a display name in the **Diagnostic setting name** dialog box.
37
+
5.Under **Destination details**, select the destination you want to use to export your IoT connector diagnostics metrics to. In the above example, we've selected an Azure storage account.
38
38
39
-
6. Under **Destination details**, select the method you want to use to access your diagnostics logs. In this example, we've selected an Azure storage account.
40
-
41
-
Diagnostics logs can be sent to the following destinations:
39
+
Diagnostics metrics can be sent to the following destinations:
42
40
43
41
|Destination|Description|
44
42
|-----------|-----------|
@@ -48,33 +46,26 @@ In this article, you'll learn how to enable IoT connector diagnostics logging.
48
46
|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.|
49
47
50
48
> [!Important]
51
-
> Each **Destination details** selection requires that certain resources (for example: an existing storage account) be created and available before the selection can be successfully configured. Click each selection to get a list of the required resources.
49
+
> 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.
52
50
53
-
7. Select **AllMetrics**
51
+
6. Select **AllMetrics**.
54
52
55
53
> [!Note]
56
-
> **AllMetrics** contains the following IoT connector metrics:
> To view a complete list of IoT connector metrics associated with **AllMetrics**, see [Microsoft.HealthcareApis/workspaces/iotconnectors](/azure/azure-monitor/essentials/metrics-supported#microsofthealthcareapisworkspacesiotconnectors).
64
55
65
-
8. Select **Save**
56
+
7. Select **Save**.
66
57
67
58
> [!Note]
68
-
> It might take up to 15 minutes for the first diagnostics logs to display in the destination of your choice.
59
+
> It might take up to 15 minutes for the first IoT connector diagnostics metrics to display in the destination of your choice.
69
60
70
-
For more information about how to work with diagnostics logs, see the [Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md)
61
+
For more information about how to work with diagnostics logs, see the [Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md).
71
62
72
63
## Conclusion
73
-
Having access to diagnostics logs is essential for monitoring and troubleshooting. IoT connector allows you to do these actions through diagnostics logging.
64
+
Having access to diagnostics metrics is essential for monitoring and troubleshooting. IoT connector allows you to do these actions through the export of diagnostics metrics.
74
65
75
66
## Next steps
76
67
77
-
Check out frequently asked questions (FAQs) about IoT connector.
68
+
To view the frequently asked questions (FAQs) about IoT connector, see
0 commit comments