The tlwebaccess log file doesn't have any correlation between log messages and therefor it's very hard to follow steps in a session and which errors is created for which session. We should consider to use session id hash which is generated on main page (login form) which follows the whole logon process, even when redirected to agent. With this we could prefix log entries with '[sessid] ...' and administrator could easily grep this on both master and agent to get all relevant logs for a login session....
Perhaps logging to the journal could help here? In that there might be some way of providing metadata that allows a sysadmin to follow a user/session.
