Incorrect edgeAgent_total_time_running_correctly_seconds metric

[tds-captic]

Expected Behavior

Following this guide led me to notice a potential bug while developing. I still had a few modules that were failing:

But strangely enough, when looking at the Workbook I saw inconsistent results related to the uptime of these modules:

At least a few of these should be close to 0.

This is the output of the iotedge list command on the IoT device itself:

The logs confirm the fact that

Current Behavior

The edgeAgent_total_time_running_correctly_seconds is not correct. It does not reflect the amount of time the module was specified in the deployment and was in the running state.

Device Information

• Host OS: Ubuntu 18.04
• Architecture: arm64
• Container OS: Linux containers

Runtime Versions

• aziot-edged: 1.4.10
• Edge Agent: 1.4
• Edge Hub: 1.4
• Docker/Moby: 20.10.25+azure-2

[yophilav]

Hi @tds-captic , Thank you for the issue report. In order for us to investigate this issue, we will need to request the logs of your systems. Could you please contact Microsoft support team to have them create an incident so we may exchange the logs securely please?

In the meantime, you can try to see what metrics we are getting from edgeAgent directly (without going through cloud/IoTHub) by doing

1. Make sure the port 9600 is exposed (see the config in the first paragraph of https://learn.microsoft.com/en-us/azure/iot-edge/how-to-access-built-in-metrics?view=iotedge-1.4 )
2. Once the port is exposed, you can run sudo docker exec edgeAgent wget -qO- edgeAgent:9600/metrics on the device which should output ALL the metrics and their values from edgeAgent.

[simondegheselle]

I am facing the same issue 😔

[yophilav]

Could you try expose the port 9600 and scrape the metrics per step 1 & 2 from the comment above? How do those metrics looking?

[yophilav]

@tds-captic Did you get a chance to try scrap and look at the edgeAgent metrics ?

[yophilav]

Close the issue due to inactivity.