Hard Filter for Debugger

Feature Request
,
1

As we continue to field devices, I’m noting that it’s becoming harder and harder to catch a single device’s publish in some of our more heavily used workflows. The ‘Debug Nodes’ have serial numbers in the message so they are filterable to the device, but we have so much throughput, I often miss the entry I need because the overall debugger queue cleanup will wipe out my debug output before I can get the primary and custom node messaging off and muted.

I’d love to be able to have a ‘Stop on First’ capability that will shut down all the debugging stream once the first one that meets my filter criteria lands. Either that or a ‘Hard Filter’ that dumps messages that don’t meet the criteria completely so they don’t contribute to the overall debug message queue limit.

2

We have an open feature request to apply that filter on the stream side and not just in the browser. I’ll add your +1 to that.

3

What if we exposed an option where, as a workflow viewer, you could provide an expression that evaluated against each generated debug payload and, if it returned true, would publish the output to the stream? This filter would be applied stream-side, unlike the filter at the top of the debug panel that just limits the displayed messages that have been sent to the browser.

For example, to only display messages where the payload contains a specific device ID (such as “123345”) at data.deviceId, you would provide an expression of {{data.deviceId}} === “12345”.

4

I think this is absolutely a solution.