Closed cherrycl closed 9 months ago
@cherrycl , I was not able to reproduce the Registration errors since it is a timing issue, but do see how this could occur. I have an idea on how to detect and ignore this issue without the need for locking, which will cause performance issue.
Error duplicate metric
was gone, but the The value of histogram-count for MqttExportSize is still incorrect. Create new issue #1540 for it.
π Bug Report
Affected Services [REQUIRED]
The issue is located in: app-service ### Is this a regression? Yes, the previous version in which this bug was not present was: Napa ### Description and Minimal Reproduction [**REQUIRED**] 1. Download the [compose file](https://raw.githubusercontent.com/edgexfoundry/edgex-compose/main/docker-compose-no-secty-with-app-sample.yml) and attached docker-compose-mqtt-broker.yml file. [docker-compose-mqtt-broker.yml.zip](https://github.com/edgexfoundry/app-functions-sdk-go/files/13896513/docker-compose-mqtt-broker.yml.zip) 2. Deploy EdgeX with the compose files `docker compose -f docker-compose-no-secty-with-app-sample.yml -f docker-compose-mqtt-broker.yml up -d`. 3. Update `app-sample/Writable/Pipeline/Functions/MQTTExport/Parameters/BrokerAddress` to `tcp://edgex-mqtt-broker:1883` by Consul GUI 4. Update `app-sample/Writable/Pipeline/ExectionOrder` to `MqttExport` by Consul GUI 5. Create new key `Writable/Telemetry/Metrics/MqttExportSize` and set value to `true` under app-sample 6. Subscribe `edgex.telemetry.app-sample.MqttExportSize` by redis-cli and wait 2 minutes to receive the MqttExportSize metric ## π₯ Exception or Error The metric value of histogram-count are always the same, but events keep exporting. ## π Your Environment **Deployment Environment:** Ubuntu / x86 **EdgeX Version [**REQUIRED**]:** Main **Anything else relevant?** `HttpExportSize`, `HttpExportErrors`, `MqttExportErrors` have the same issue.