# Network monitoring : is there a way to monitor network traffic to and from Node-RED in a fine-grained way?

**URL:** <https://discourse.nodered.org/t/network-monitoring-is-there-a-way-to-monitor-network-traffic-to-and-from-node-red-in-a-fine-grained-way/19780>\
**Category:** General\
**Created:** [31 December 2019 17:08 UTC](https://discourse.nodered.org/t/network-monitoring-is-there-a-way-to-monitor-network-traffic-to-and-from-node-red-in-a-fine-grained-way/19780 "2019-12-31T17:08:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nicholas](https://avatars.discourse-cdn.com/v4/letter/n/4da419/32.png) [@nicholas](https://discourse.nodered.org/u/nicholas)\
**Post date:** [31 December 2019 17:08 UTC](https://discourse.nodered.org/t/network-monitoring-is-there-a-way-to-monitor-network-traffic-to-and-from-node-red-in-a-fine-grained-way/19780/1 "2019-12-31T17:08:50Z")

</div>

Howdy folks!

I've searched the forum and library for clues to this question, but didn't see anything specifically addressing it:

I maintain several N-R instances with many flows each. With something like nethogs, I can see network traffic volume to and from a N-R instance _in general_ , but not to see which flows / nodes / etc are sending or receiving that traffic.

Is there a way for me to see this Tx / Rx information in a more fine-grained way, broken down at the flow or node level?

Thanks and happy New Year,

Nicholas

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [1 January 2020 16:09 UTC](https://discourse.nodered.org/t/network-monitoring-is-there-a-way-to-monitor-network-traffic-to-and-from-node-red-in-a-fine-grained-way/19780/2 "2020-01-01T16:09:52Z")

</div>

Viewed from the outside, there is little information that relates traffic to a specific node though if you are monitoring msg's via MQTT, websocket or another network transmission method, then you will have the `_msgid` property.

HTTP traffic from one of the UI's (the Editor for administration, or /ui for Dashboard, etc) again will not be easily relatable though in the Editor, I think that most nodes will have an ID that should be relatable.

Probably the easiest (and it isn't that easy - at least for a non-pro developer like me) method is to start up Node-RED with node.js's `--inspect` parameter. Then you can use something like VScode or one of the Chromium-based browsers (Vivaldi is good for example) to monitor the code as it executes.