# Node Traffic Monitoring

**URL:** <https://discourse.nodered.org/t/node-traffic-monitoring/42586>\
**Category:** General\
**Created:** [13 March 2021 15:14 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586 "2021-03-13T15:14:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![eddee54455](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/eddee54455/32/43350_2.png) [@eddee54455](https://discourse.nodered.org/u/eddee54455)\
**Post date:** [13 March 2021 15:14 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586/1 "2021-03-13T15:14:41Z")

</div>

Good day learned fellows...

I am trying to find out if there is a dashboard/status/Info screen that lists the traffic through nodes on a "live" basis...

I have a situation developing where "node-traffic" (I think) grabs a fair bit of horsepower on occasion at irregular intervals from the pi and I would like to see where the traffic is heaviest to try and sort it out....

Any Suggestions?

Cheers  
Ed

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [13 March 2021 15:33 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586/2 "2021-03-13T15:33:56Z")

</div>

Hi Ed,  
You can use my [node-red-contrib-msg-speed](https://github.com/bartbutenaers/node-red-contrib-msg-speed) node to measure how many messages per time unit pass through a wire. And recently I have published the [node-red-contrib-msg-size](https://github.com/bartbutenaers/node-red-contrib-msg-size) node, which allows to measure how many bytes per time unit pass through a wire (to measure the throughput).  
Bart

---

<div class="post-metadata">

**Author:** ![eddee54455](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/eddee54455/32/43350_2.png) [@eddee54455](https://discourse.nodered.org/u/eddee54455)\
**Post date:** [13 March 2021 15:42 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586/3 "2021-03-13T15:42:42Z")

</div>

Hi Bart,

Thanks for coming back to me!

Unfortunately my "little" project has got a bit large...

I need a more "global" approach to try and find the bottlenecks... Pretty much like the "top" or "htop" functions... Once I can find the busy nodes, then for the deeper analysis your goodies would be A1!!

Any ideas on how to do this? Is it even possible?

Regds  
Ed

---

<div class="post-metadata">

**Author:** ![BartButenaers](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/bartbutenaers/32/10476_2.png) [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)\
**Post date:** [13 March 2021 15:48 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586/4 "2021-03-13T15:48:10Z")

</div>

That has been asked a couple of times in the past. Don't think it is possible, based on those discussions.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [13 March 2021 15:55 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586/5 "2021-03-13T15:55:27Z")

</div>

In settings.js you can turn on metrics - this is will log a much finer level of timing detail. However we have been waiting for many years for someone to create a nice analyser for that log 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [12 May 2021 15:56 UTC](https://discourse.nodered.org/t/node-traffic-monitoring/42586/6 "2021-05-12T15:56:18Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.