(Oops, I have not captured all the message here, but as an example)
Is there a way to know anything more about from where this message came?
You know what node has logged it. What path it took to get there isn't anything we can help with.
If that's information you need, then you should make sure the flows that send that message include some sort of identifier that is meaningful to you.
1 Like
Not the end of the world.
this actually refers to a generic concept that node-red doesnt currently support out of the box, that is Data Provenance. This is not to say that Data Provenance is something that was considered a need anyway by the use cases of the project as I gathered. Also it does not mean it cannot be done, but this is a core design point. Also I don't necessarily suggest node-red should have support or a solution to this either at least for now! With the addition of node-red-debugger, this is now getting easier and with some custom work in the flow, it can be achieved but it is quite a task imho. However, in large enterprise projects and if the application is used particularly in data management of critical data, data provenance becomes extremely important in supporting compliance, optimization and troubleshooting. I had to go through this route in one project. I guess this is a different topic altogether but it was one of those things that I struggled with at the start..
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
