3 ms·

I'm working on it as we speak! My plan is to listen on multiple ports then attach the "origin" field to each log message with the port number it was produced wi

I'm working on it as we speak! My plan is to listen on multiple ports then attach the "origin" field to each log message with the port number it was produced with. This way you should be able to do: $ logdy socket 8001,8002,8003 $ node app1.js | nc 8001; $ node app2.js | nc 8002; $ node app3.js | nc 8003; Wdyt?

pmig 3y ago
Makes sense! I like the approach.
zokier 3y ago
Not sure if you want to go that route, but unix sockets allow you to use SO_PASSCRED to get the pid of the connected process, you could use that as natural "origin" without requiring many ports