-
Notifications
You must be signed in to change notification settings - Fork 851
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[core] Minor connection logging improvement. #2930
[core] Minor connection logging improvement. #2930
Conversation
Also downgraded some logs from 'note' to 'debug'.
Do we see where the group is created in these logs or we need to catch the first add? |
There's a log from
@ and $ are intended to mark the bare number as being the socket or group id respectively, so in that light rather the "member" and "group" words might be redundant. I'd leave the "member" word there though for clarity. Not sure what this hex would be useful for. The decimal encoding for the socket and group ID is being used in these logs everywhere. For Wireshark we have also submitted a fix that should show them in decimal. |
Just like Mikolaj said, at some point we decided to make Socket IDs consistent in logs and switched to decimal format, including srt-xtransmit and Wireshark. |
Maybe this log should become a regular one with "note"-level.
|
Also downgraded some logs from 'note' level to 'debug'.
Also downgraded some logs from 'note' level to 'debug'.
Also downgraded some logs from 'note' level to 'debug'.
It is not clear from SRT logs which SRT socket ID is associated with which local and remote IP. It is even more viable in group connections. Therefore a 'note'-level log message has been added one a connection is accepted by the listener.
Some logs were downgraded from 'note' to 'debug'.
Before
After
Listener
Caller
To Consider
@121901312: listen ret: -1 - conclusion
should also be Debug-level log message.