# FR: Debug directly on node output
**URL:** https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812
**Category:** Feature Requests
**Created:** [5 February 2022 05:40 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812 "2022-02-05T05:40:57Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@quarfie](https://discourse.nodered.org/u/quarfie)
#### Post date: [5 February 2022 05:40 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/1 "2022-02-05T05:40:57Z")
When developing flows, I find myself with many debug nodes taking up a lot of space on the tab.
I wonder if the functionality of the Debug node could be delivered as an attribute of every node output.
It might look similar to the breakpoint used by the Node-RED flow debugger, but green of course!
I imagine that you might add/remove the debug feature by double-clicking the node output. And by double-clicking the green area, you would open the properties dialog just like the Debug node has.
---
### Author:  [@BartButenaers](https://discourse.nodered.org/u/BartButenaers)
#### Post date: [5 February 2022 07:07 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/2 "2022-02-05T07:07:25Z")
Morning @quarfie,
Personally I like this idea a lot. Two remarks:
> [@quarfie](#):
>
> delivered as an attribute of every node output
Is there any reason why you want to apply it only to outputs. Because if you have a N-to-1 node relation (with a large N) then it would be usefull to have it also on inputs imho..
> [@quarfie](#):
>
> by double-clicking the green area, you would open the properties dialog
Yes if you would have such a property dialog, you would be able to add - in the future - other features. For example a checkbox _"Add routing info to msg"_. To support something like discussed [here](https://discourse.nodered.org/t/announce-node-red-contrib-msg-profiler-1-0-0-beta/54609)? Just to mention why I like your proposal...
---
### Author:  [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [5 February 2022 08:15 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/3 "2022-02-05T08:15:40Z")
Hi @quarfie
Thanks for the suggestion.
Being able to more easily 'inspect' a flow is certainly something we're interested in.
Being able to debug ports directly, with out having to wire in nodes, has come up previously.
---
### Author:  [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [5 February 2022 08:53 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/4 "2022-02-05T08:53:07Z")
This sounds like an enhancement to the debugger plugin to me
---
### Author:  [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [5 February 2022 12:05 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/5 "2022-02-05T12:05:25Z")
And I do like Bart's idea for being able to debug inputs as well as outputs.
---
### Author:  [@LosinIt](https://discourse.nodered.org/u/LosinIt)
#### Post date: [5 February 2022 13:45 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/6 "2022-02-05T13:45:45Z")
Precisely because I'm _ **not** _ a power user I like this idea _and_ Bart's profiler.
---
### Author:  [@system](https://discourse.nodered.org/u/system)
#### Post date: [6 April 2022 13:46 UTC](https://discourse.nodered.org/t/fr-debug-directly-on-node-output/57812/7 "2022-04-06T13:46:34Z")
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.