Currently the only way to differentiate each thread by log messages is by knowing that there is a separate thread per observer / slave. Ex:
Aug 19 17:45:48 [DEBUG] switchy.EventListener@vm-host.qa.sangoma.local observe.py:901 : all sessions for call 'a4a34890-46bb-11e5-8351-74d02bc595d7' were hung up
Aug 19 17:46:08 [DEBUG] switchy.EventListener@sip-cannon.qa.sangoma.local observe.py:544 : receive event 'CHANNEL_HANGUP'
The only indicator is the slave's hostname info found after the class name which for this example are vm-host and sip-cannon respectively.
There should probably be an additional indicator (maybe the thread id?) such that a user knows immediately from which thread a message has been emitted. This is handy especially when reading messages from the Originator burst loop thread which, currently has no indicator other then it being different in format then the observer produced messages.
moises-silva
commented
8 years ago
Currently the only way to differentiate each thread by log messages is by knowing that there is a separate thread per observer / slave. Ex:
The only indicator is the slave's hostname info found after the class name which for this example are
vm-hostandsip-cannonrespectively.There should probably be an additional indicator (maybe the thread id?) such that a user knows immediately from which thread a message has been emitted. This is handy especially when reading messages from the
Originatorburst loop thread which, currently has no indicator other then it being different in format then the observer produced messages.It usually looks something like: