feat(trace): add node_red.flow.name span attribute#28
Merged
Conversation
czepiec
force-pushed
the
feat-flow-name
branch
3 times, most recently
from
March 31, 2026 21:06
8398a18 to
61ee20d
Compare
Resolve flow tab name from flow id using RED.nodes.getNode API and include it in common span attributes for better observability.
czepiec
marked this pull request as ready for review
March 31, 2026 21:18
Owner
|
Thank you for this proposal. Released in 1.6.4 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
node_red.flow.nameattribute to all spans by resolving the flow tab label from the node's_flow.flow.labelreference.Motivation
Flow name is essential for practical observability in Node-RED:
Implementation notes
nodeDefinition._flow.flow.label— an internal (non-enumerable) property on node objects, available since Node-RED 0.20 (2019)The changes are tested and we are using them in our large-scale Node-RED v4.0.9 instance.