延迟时间戳 [英] Delay in Timestamps
问题描述
您好，
我通过IOT网关从OPCUA服务器向Azure Data Lake发送消息。我已经看到de Source Timestamp（由OPC服务器生成）和IoT Hub在云中生成的IoTHub.EnqueuedTime之间的差异越来越大。
这两个时间戳之间的差异每小时增加4-5秒。我已经做了几次不同数量的项目和频率的试验，但差距越来越大。
谁能告诉我为什么会发生这种情况？我在哪里可以检查以避免这个项目？
提前致谢
Pedro
嗨佩德罗，
我可以看到很多因素这可能会影响您提到的延迟：
- 从OPCUA服务器到IoTHub的网络连接
- IoTHub由于配额而限制消息
- 应用程序上的多线程并发或内存不足问题。
- ...
为了更好地帮助您解决此问题，我需要了解您使用的OPCUA服务器是什么？是 iot-edge-opc-publisher ？什么版本？它是在windows
还是linux上运行的？还是在码头工作？ Linux或Windows容器？
如果使用 iot-edge-opc-publisher 还请利用其中的问题部分： https://github.com/Azure/ iot-edge-opc-publisher / issues
谢谢！
Hello,
I am sending messages from an OPCUA server to a Azure Data Lake through a IOT Gateway. I've seen that there is a growing difference between de Source Timestamp (generated by the OPC server) and the IoTHub.EnqueuedTime, generated by IoT Hub, in the cloud. The difference between these two timestamps grows about 4-5 seconds each hour. I have done several trials with different number of items and frequencys, but the gap coes on growing.
Can anyone tell me why can this be happening? where can i check to avoid this item?
Thanks in advance
Pedro
Hi Pedro,
I can see many factors that may influence the delay you mention:
- Network connection from your OPCUA server up to IoTHub
- IoTHub throttling messages due to quota
- Multi thread concurrency on your application or out of memory issues.
- ...
In order to better help you troubleshooting this issue I need to understand what are you using as your OPCUA server? Is it iot-edge-opc-publisher ? What version? Is it running on windows or linux? Or is it running in docker? Linux or windows container?
If using iot-edge-opc-publisher please also leverage the issues section there: https://github.com/Azure/iot-edge-opc-publisher/issues
Thank you!
这篇关于延迟时间戳的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
