# DEBUG window suggestion

**URL:** <https://discourse.nodered.org/t/debug-window-suggestion/87383>\
**Category:** Feature Requests\
**Created:** [21 April 2024 11:16 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383 "2024-04-21T11:16:11Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [21 April 2024 11:16 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/1 "2024-04-21T11:16:11Z")

</div>

In light of information given to me here:

> [@Interesting / weird observation in DEBUG window (NR 3.0.2)](https://discourse.nodered.org/t/interesting-weird-observation-in-debug-window-nr-3-0-2/87382/3):
>
> I didn't know that. Thanks.

There seems - to me - a problem.

_You_ are working on a `tab` and have selected the `debug` to display only message from that tab to reduce being overwhelmed my any other messages......

But the messages displayed are being wiped because the messages from other tabs - which are not being displayed - are pushing the ones you want to see off the screen.

To me that is not helpful.  
:shrug:

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [21 April 2024 11:30 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/2 "2024-04-21T11:30:21Z")

</div>

Disable the other debug nodes. There is no point having loads of debug nodes active, you are just wasting bandwidth and CPU.

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [21 April 2024 11:48 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/3 "2024-04-21T11:48:14Z")

</div>

Well, yes and no.

And I kind of hear what you are saying.

But to me the filtering is being done _too late_ in the scheme of things.

I leave the `debug` nodes active as they are _key points_ in that `tab`'s layout and if I need to debug that tab, it is nice to have those tabs active.

Your way I am going to have to disable all the other nodes on all the other tabs which goes against the benefit/idea of having them filtered.

---

<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:** [21 April 2024 13:36 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/4 "2024-04-21T13:36:41Z")

</div>

I get what you are saying. And maybe someone will work out a better debug view in the future if someone has the time and inclination.

For me, I tend to disable the debug nodes if I want to keep the layout and know that I might want them again in the future. Just so that I know they are not sucking up resources. Not perfect but enough.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [21 April 2024 13:51 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/5 "2024-04-21T13:51:19Z")

</div>

I don't know if there are plans to improve debug nodes.

In the meantime, here is a [suggested approach](https://discourse.nodered.org/t/output-to-debug-window-disappears-too-fast/86316/12)

It's not the slightest bit elegant but has some advantages

- You replace all debug nodes with a simple link to a central debug flow (or sublflow?).
- You can restrict those messages which get displayed according to msg.topic
- You can allow or prohibit any where msg.topic is not included in the filter list.

---

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [21 April 2024 13:58 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/6 "2024-04-21T13:58:00Z")

</div>

Perhaps a better idea is a debug flow with multiple entry links representing debug priority:

![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/1/1/11040f0975f6072388dd53ad55c3192ef0cb99a2.png)

---

<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:** [21 April 2024 15:42 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/7 "2024-04-21T15:42:47Z")

</div>

Indeed. And I've previously used (and published I think) flows that output debug info to a separate uibuilder web page.

As always, Node-RED has many ways of achieving things.

---

<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:** [20 June 2024 15:43 UTC](https://discourse.nodered.org/t/debug-window-suggestion/87383/8 "2024-06-20T15:43:17Z")

</div>

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