Improve logging from Locationmap

• Key: FOR-702
• Type: Improvement
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Ross Gardler
• Reporter: Ross Gardler
• Component/s: Locationmap
• Fix Version/s: 0.8

Description

Debugging locationmaps is currently very difficult as no log information is provided.

We need the following debug log entries:

- for matches - record all entries encountered
- for select statements, record all entries being tested

Comments

[David Crossley]

Sorry don't understand what you mean. Did you raise the log level in WEB-INF/logkit.xconf file? .... you said "no log information is provided".

Or do you want "extra" information to be logged?

[Tim Williams]

Is this still an issue? Someone has apparently improved this significantly. I just turned on debugging and was pleasantly suprised to see some good info being logged. Is there something more specific that is needed with this issue?

[Ross Gardler]

Yeah, I've been working on it periodically as I work on Locationmaps. Basically, if I find a problem I can't solve I add logging.

I've not found such a problem for a while, so maybe this issue can be closed, but not yet...

Right now the locatonmap logs are being duplicated in the linkrewriter, the locationmap and the core logs. This is a waste of resources, we need to make them appear in just the locationmap log. I guess this is a logkit.xconf setting

[David Crossley]

Re: Comment [06/Dec/05 10:40 AM]
The logkit.conf issue is followed up here:
 http://marc.theaimsgroup.com/?l=forrest-dev&m=11339125672532
 Re: tuning the logfiles

[David Crossley]

There used to be an issue that, if a match is not found, then no actual error is recorded - the request sort of silently falls out the end of the locationmap. Not sure if that can even be helped.

Also there is the related issue FOR-701 "Missing locationmap entry gives poor error"

[Ross Gardler]

Resolving this issue, logs are fairly good now.