Skip to content

Commit 8399227

Browse files
committed
Add pointer to IoT Edge DPS client error from DPS troubleshooting
1 parent 38bf76e commit 8399227

File tree

1 file changed

+10
-9
lines changed

1 file changed

+10
-9
lines changed

articles/iot-dps/how-to-troubleshoot-dps.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,18 @@
11
---
2-
title: Diagnose and troubleshoot disconnects with Azure IoT Hub DPS
3-
description: Learn to diagnose and troubleshoot common errors with device connectivity for Azure IoT Hub Device Provisioning Service (DPS)
4-
author: xujing-ms
5-
manager: nberdy
2+
title: Diagnose and troubleshoot provisioning errors with Azure IoT Hub DPS
3+
description: Learn to diagnose and troubleshoot common errors for Azure IoT Hub Device Provisioning Service (DPS)
4+
author: kgremban
65
ms.service: iot-dps
76
services: iot-dps
87
ms.topic: conceptual
9-
ms.date: 04/15/2022
10-
ms.author: xujing
11-
#Customer intent: As an operator for Azure IoT Hub DPS, I need to know how to find out when devices are disconnecting unexpectedly and troubleshoot resolve those issues right away.
8+
ms.date: 05/25/2022
9+
ms.author: kgremban
10+
#Customer intent: As an operator for Azure IoT Hub DPS, I need to know how to find out when devices are not being provisioned and troubleshoot and resolve those issues right away.
1211
---
1312

1413
# Troubleshooting with Azure IoT Hub Device Provisioning Service
1514

16-
Connectivity issues for IoT devices can be difficult to troubleshoot because there are many possible points of failures such as attestation failures, registration failures etc. This article provides guidance on how to detect and troubleshoot device connectivity issues via Azure Monitor. To learn more about using Azure Monitor with DPS, see [Monitor Device Provisioning Service](monitor-iot-dps.md).
15+
Provisioning issues for IoT devices can be difficult to troubleshoot because there are many possible points of failures such as attestation failures, registration failures, etc. This article provides guidance on how to detect and troubleshoot device provisioning issues via Azure Monitor. To learn more about using Azure Monitor with DPS, see [Monitor Device Provisioning Service](monitor-iot-dps.md).
1716

1817
## Using Azure Monitor to view metrics and set up alerts
1918

@@ -27,7 +26,7 @@ To view and set up alerts on IoT Hub Device Provisioning Service metrics:
2726

2827
4. Select the desired metric. For supported metrics, see [Metrics](monitor-iot-dps-reference.md#metrics).
2928

30-
5. Select desired aggregation method to create a visual view of the metric.
29+
5. Select desired aggregation method to create a visual view of the metric.
3130

3231
6. To set up an alert of a metric, select **New alert rules** from the top right of the metric blade, similarly you can go to **Alert** blade and select **New alert rules**.
3332

@@ -68,6 +67,8 @@ Use this table to understand and resolve common errors.
6867
| 429 | Operations are being throttled by the service. For specific service limits, see [IoT Hub Device Provisioning Service limits](../azure-resource-manager/management/azure-subscription-service-limits.md#iot-hub-device-provisioning-service-limits). | 429 Too many requests |
6968
| 500 | An internal error occurred. | 500 Internal Server Error|
7069

70+
If an IoT Edge device fails to start with error message `failed to provision with IoT Hub, and no valid device backup was found dps client error.`, see [DPS Client error](/azure/iot-edge/troubleshoot-common-errors?view=iotedge-2018-06&preserve-view=true#dps-client-error) in the IoT Edge (1.1) documentation.
71+
7172
## Next Steps
7273

7374
- To learn more about using Azure Monitor with DPS, see [Monitor Device Provisioning Service](monitor-iot-dps.md).

0 commit comments

Comments
 (0)