Open smalls12 opened 6 years ago
The recently added v2 monitoring events now allow identifying the connection an event is referring to showing both the source and destination (e.g. TCP) addresses, however it does not (yet) contain the routing id. The event format is now more flexible, so this information could be added.
Hi @sigiesec,
Just wondering if this has been taken any further re: adding routing id. Is there any particular place I should start looking to see how difficult it would be to add it in?
Thanks :)
After discussions in #3213, decided that this could use its own thread for discussions.
3213 provided a new feature that would allow a ROUTER socket detect when a DEALER disconnects.
The idea was floated about how this could be integrated into the socket monitor as this is its primary function.
The socket monitor can already process events from the ROUTER socket, but does not currently provide some sort of mechanism to identify which DEALER that event is for.