Skip to content

Commit c7f788b

Browse files
committed
Updating article and adding back to IoT TOC
1 parent 58eb3bb commit c7f788b

8 files changed

+34
-19
lines changed

articles/healthcare-apis/iot/iot-metrics-diagnostics-export.md

Lines changed: 32 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,56 +1,69 @@
11
---
2-
title: Export IoT connector Metrics through Diagnostic settings - Azure Healthcare APIs
3-
description: This article explains how to export IoT connector metrics through Diagnostic settings
2+
title: Enable IoT connector metrics logging through Diagnostic settings - Azure Healthcare APIs
3+
description: This article explains how to log IoT connector metrics through Diagnostic settings
44
services: healthcare-apis
55
author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: how-to
9-
ms.date: 11/10/2021
9+
ms.date: 1/20/2021
1010
ms.author: jasteppe
1111
---
1212

13-
# Export IoT connector Metrics through Diagnostic settings
13+
# Enable IoT connector metrics through Diagnostic settings
1414

1515
> [!IMPORTANT]
1616
> 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.
1717
18-
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.
18+
In this article, you'll learn how to enable IoT connector metrics logs. The feature that enables metrics logging is the [**Diagnostic settings**](../../azure-monitor/essentials/diagnostic-settings.md) in the Azure portal.
1919

20-
## Enable Metrics logging for IoT connector
21-
1. To enable Metrics logging for the IoT connector, select your Fast Healthcare Interoperability Resources (FHIR®) service in the Azure portal.
20+
## Enable metrics logging exporting for IoT connector
21+
1. To enable metrics logging for IoT connector, select **IoT connector** in your Workspace.
22+
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":::
2224

23-
2. Navigate to **Diagnostic settings**
25+
2. Select the IoT connector that you want to enable metrics logging for.
26+
27+
:::image type="content" source="media/iot-metrics-export/iot-connector-logging-select-connector.png" alt-text="Select IoT connector for enabling logging" lightbox="media/iot-metrics-export/iot-connector-logging-select-connector.png":::
2428

25-
3. Select **+ Add diagnostic setting**
29+
3. Select the **Diagnostic settings** button and then select the **+ Add diagnostic setting** button.
2630

27-
:::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":::
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":::
2832

2933
4. Enter a name in the **Diagnostic setting name** dialog box.
3034

31-
5. Select the method you want to use to access your diagnostic logs:
35+
5. Under **Destination details**, select the method you want to use to access your diagnostic logs. In this example, we have selected an Azure storage account.
36+
37+
> [!Important]
38+
> 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 required resources.
3239
33-
1. **Archive to a storage account** for auditing or manual inspection. The storage account you want to use needs to be already created.
34-
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.
35-
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.
40+
6. Select **Allmetrics**
3641

37-
6. Select **Errors, Traffic, and Latency** for IoT connector. Select any extra metric categories you want to capture for the FHIR service.
42+
> [!Note]
43+
> **Allmetrics** contains the following IoT connector metrics:
44+
> * TotalErrors
45+
> * DeviceEvent
46+
> * NormalizedEvent
47+
> * Measurement
48+
> * MeasurementGroup
49+
> * DeviceEventProcessingLatencyMs (Ms = millisecond)
50+
> * MeasurementIngestionLatencyMs (Ms = millisecond)
3851
3952
7. Select **Save**
4053

41-
:::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":::
54+
:::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":::
4255

4356
> [!Note]
44-
> It might take up to 15 minutes for the first Metrics logs to display in the repository of your choice.
57+
> It might take up to 15 minutes for the first metrics logs to display in the destination of your choice.
4558
4659
For more information about how to work with diagnostic logs, see the [Azure Resource Log documentation](../../azure-monitor/essentials/platform-logs-overview.md)
4760

4861
## Conclusion
49-
Having access to Metrics logs is essential for monitoring and troubleshooting. IoT connector allows you to do these actions through Metrics logs.
62+
Having access to metrics logs is essential for monitoring and troubleshooting. IoT connector allows you to do these actions through metrics logging.
5063

5164
## Next steps
5265

53-
Check out frequently asked questions about IoT connector.
66+
Check out frequently asked questions (FAQs) about IoT connector.
5467

5568
>[!div class="nextstepaction"]
5669
>[IoT connector FAQs](iot-connector-faqs.md)
Binary file not shown.
32.9 KB
Loading
51.5 KB
Loading
58.6 KB
Loading
83.1 KB
Loading

articles/healthcare-apis/iot/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,6 +50,8 @@ items:
5050
href: how-to-use-fhir-mappings.md
5151
- name: Display Metrics
5252
href: how-to-display-metrics.md
53+
- name: Enable diagnostics logging
54+
href: iot-metrics-diagnostics-export.md
5355
- name: Create copies of mappings
5456
href: how-to-create-mappings-copies.md
5557
- name: Concepts

0 commit comments

Comments
 (0)