agent call logging
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Satega |
Fix Released
|
Low
|
bernhard |
Bug Description
the agent is logging each request but it does not log which method is called.
Here is a patch which enhances this.
OLD:
2009-02-03 19:21:25 INFO SategaCD module activated
2009-02-03 19:21:25 INFO MusicServer module activated
2009-02-03 19:21:25 INFO Listening on: 127.0.0.1:8000
localhost - - [03/Feb/2009 19:21:26] "POST /RPC2 HTTP/1.0" 200 -
localhost - - [03/Feb/2009 19:21:26] "POST /RPC2 HTTP/1.0" 200 -
localhost - - [03/Feb/2009 19:21:26] "POST /RPC2 HTTP/1.0" 200 -
localhost - - [03/Feb/2009 19:21:26] "POST /RPC2 HTTP/1.0" 200 -
localhost - - [03/Feb/2009 19:21:26] "POST /RPC2 HTTP/1.0" 200 -
NEW
2009-02-03 19:26:18 INFO LogInspect module activated
2009-02-03 19:26:18 INFO SategaCD module activated
2009-02-03 19:26:18 INFO MusicServer module activated
2009-02-03 19:26:18 INFO Listening on: 127.0.0.1:8000
2009-02-03 19:26:20 INFO SategaCd backupDbBin
2009-02-03 19:26:20 INFO SategaCd backupDbBin
2009-02-03 19:26:20 INFO SategaCd getDbPath
2009-02-03 19:26:20 INFO SategaCd deleteBackupDb
2009-02-03 19:26:20 INFO SategaCd install
2009-02-03 19:26:20 INFO SategaCd isInstalled
2009-02-03 19:26:20 INFO SategaCd restoreDbBin
2009-02-03 19:26:20 INFO SategaCd restoreDbBin
Great. I've been annoyed with the xmlserver logging which you turned off using server. logRequests= 0 :-)
Logging each server request is probably not needed, we can maybe do it as debug.logging, and when installing satega, we configure logging of info, warning and error.
For bug-tracking, we can enable turning on debug-logging from the gui.
Will you include your diff in your branch, or do you want me to?
-s