Hi Sai ,
It's a fascinating question, and we encountered a similar issue a few days ago with Azure Stream Analytics module version 1.0.12. Interestingly, we didn't experience this problem with the previous version, 1.0.9. To address this situation, we took the following approach: we employed the 'nload' command on our edge gateway to perform a comparative analysis and monitor both incoming and outgoing network traffic.
Nload Command :
The 'nload' command is a powerful and handy network monitoring tool used to visualize incoming and outgoing traffic on a network interface in real-time. It provides a graphical representation of network usage, making it easier to identify traffic patterns, diagnose issues, and monitor network performance. By using 'nload,' you can gain valuable insights into how data flows through your network interfaces, helping you make informed decisions and troubleshoot network-related problems effectively.
sudo apt install nload
The above command will install the nload in your edge gateway , and after that you can able to check the network traffic of any module you want to monitor : for example
nload -i <interface_or_module_name>
Once the above command got executed you will get the details regarding the Incoming and Outgoing traffic of a particular module as mentioned and highlighted in the below screenshot .
So this is the way we can able to monitor the incoming and outgoing network traffic of a particular edge module in the edge gateways and after that if any alerts we need to send to the respective endpoint we can make use of iotedgemetricscollector module , if you want to know more about iotedgemetricscollectormodule kindly find the microsoft learn link provided below
Hope the above information is useful. Please let us know if you have any additional questions or need further assistance and if the answer provided above resolves your issue means please do upvote and accept the answer , thank you Sai !!!.