Bug 5092 - Difficult to see related log lines from tlwebaccess
Summary: Difficult to see related log lines from tlwebaccess
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Web Access (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Peter Åstrand
Depends on:
Reported: 2014-04-15 09:48 CEST by Henrik Andersson
Modified: 2023-01-25 14:37 CET (History)
0 users

See Also:
Acceptance Criteria:


Description Henrik Andersson cendio 2014-04-15 09:48:31 CEST
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....
Comment 1 Pierre Ossman cendio 2023-01-25 14:37:35 CET
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.

Note You need to log in before you can comment on or make changes to this bug.