Enhancement
If an error is displayed on the GUI, this is often done by means of a dialog in which it is stated that the administrator should be contacted. The administrator then has to laboriously rummage through the log to find out which of the entries belongs to the error.
Improvement
Log entries should contain the ID of the session from which they were logged. The administrator can then filter the logs using this session ID to find the log entries of the person who is currently reporting the error.
In ticket #27736, this feature is used to display the log of the current session in the application.
Delimitation
- The session is not displayed in Ganymede and other log viewers connected via socket, as they do not use the log pattern. However, this is not a problem because such log viewers are only used on developer computers on which several people are not logged in at the same time anyway.
- The session ID is only written if there is also a session. No session is logged before login.
- In addition, no session ID is written in background services. Sufficient filtering is already possible there via the class ("Category") and the thread.
- Exceptions that occur in the session but are only logged outside the session also have no session ID in the log.
Implementation
The session ID is written at the beginning of the log message in S(...):
Test
- Go to the following view in the demo: Technical Demo > Layout Framework #1 > Forms > Error Page.
- In the Administration > Technical administration > Log files > Log entries view, check whether this error message starts with a suitable session ID.