I have a recent issue with DPS registration requests, giving me error ” {“Message”:”{“errorCode”:401002,”message”:”The specified SAS token has an invalid signature. It does not match either the primary or secondary key.”,”trackingId”:”E377D48366F943E189A5FEA744D89D95-G2:-TimeStamp:2025-01-03T14:15:03.453324531Z”,”timestampUtc”:”2025-01-03T14:15:03.453324531Z”,”info”:null}”,”ExceptionMessage”:””}”.

I have a recent issue with DPS registration requests, giving me error ” {“Message”:”{“errorCode”:401002,”message”:”The specified SAS token has an invalid signature. It does not match either the primary or secondary key.”,”trackingId”:”E377D48366F943E189A5FEA744D89D95-G2:-TimeStamp:2025-01-03T14:15:03.453324531Z”,”timestampUtc”:”2025-01-03T14:15:03.453324531Z”,”info”:null}”,”ExceptionMessage”:””}”.

I have a recent issue with DPS registration requests, giving me error ” {“Message”:”{“errorCode”:401002,”message”:”The specified SAS token has an invalid signature. It does not match either the primary or secondary key.”,”trackingId”:”E377D48366F943E189A5FEA744D89D95-G2:-TimeStamp:2025-01-03T14:15:03.453324531Z”,”timestampUtc”:”2025-01-03T14:15:03.453324531Z”,”info”:null}”,”ExceptionMessage”:””}”.

I am using a Jetson Orin nano board as an edge device with a simulated temperature sensor module and IoT Metrics Collector module deployed. I would like to know how to collect temperature readings from the simulated sensor module using the metrics collector module and expose them via a port for use with prometheus or node exporter. Is this possible? If so, how can I achieve it?

I am using a Jetson Orin nano board as an edge device with a simulated temperature sensor module and IoT Metrics Collector module deployed. I would like to know how to collect temperature readings from the simulated sensor module using the metrics collector module and expose them via a port for use with prometheus or node exporter. Is this possible? If so, how can I achieve it?

Our custom IoTEdge module was functioning correctly until recently, when it started experiencing loss of connectivity, with our ConnectionStatusChangeHandler reporting status “ConnectionStatus.Disconnected” and reasons “ConnectionStatusChangeReason.Retry_Expired” and
ConnectionStatusChangeReason.Communication_Error”.