Improve network/Socket(IO) logging (#1198)

Activities

wojciech.kapcia@tigase.net opened 4 years ago

In #servers-319 @andrzej.wojcik improved logging for disconnected sockets to help with identification of them to avoid Socket[unconnected]. However, it's not ideal - in connected sockets i leads to duplication of information (10.0.4.39_26272_89.238.76.44_5269/355be644-5f6a-4b3a-b58c-0d024e9f24ed Socket[addr=/89.238.76.44,port=5269,localport=26272]) without much benefit.

It would be better to cache Socket output in tigase.io.SocketIO#toString (and indicated whether it's connected/disconnected) and as a logID use CID/JID (if available) and UUID

wojciech.kapcia@tigase.net commented 4 years ago

change slightly connectionId in IOService to favour CIDs in case of s2s connection (with UUID added there constantly)
- pass the ID to the SocketIO and include it in the logs as well
switched all CM logs and placed service information/debug last so the actual log entry message would be readily visible

Type	Task
Priority	Minor
Assignee	wojciech.kapcia@tigase.net
Version	tigase-server-8.2.0
Spent time	8h 30m

tigase-private/systems-maintenance/servers#319 You are not authorized to access this issue

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#1198