Updates for monitoring and troubleshooting Azure IoT Hub message routing
Published date: June 24, 2020
Several updates to Azure IoT Hub message routing help reduce the learning curve and accelerate monitoring and troubleshooting.
Key updates include:
- Multidimensional, per-endpoint monitoring metrics are now available in Azure Monitor to help you identify metrics for each endpoint and gain more details to diagnose issues faster.
- Diagnostic logs are now more descriptive and provide details on operation names and error codes.
- The Get Endpoint Health API has been enhanced to respond with the last known error, last send attempt, last failure, and last successful send attempt. This update helps you identify and debug endpoint issues faster, and also provides mitigation techniques for each last known error.
- The Get Endpoint Health API includes a new health status for endpoints. The “degraded” status indicates that the endpoint is accepting messages slower than expected or is recovering from an unhealthy state.
- Message routing via the Azure portal has been updated with more clarity on limitations of routing and experiences with built-in endpoints and fallback routes.
- A new troubleshooting guide provides mitigation methods for common debugging scenarios in IoT Hub.