MapGuide RFC 49 - Enhance Server Error and Trace Logs

This page contains an change request (RFC) for the MapGuide Open Source project. More MapGuide RFCs can be found on the RFCs page.

Status

RFC Template Version	(1.0)
Submission Date	June 16, 2008
Last Modified	Trevor Wekel Timestamp
Author	Trevor Wekel
RFC Status	not reader for review
Implementation Status	pending
Proposed Milestone	1.2, 2.0, 2.1
Assigned PSC guide(s)	(when determined)
Voting History	June 23, 2008
+1
+0
-0
-1
no vote

Overview

This proposal enhances the Server Error and Trace logs to include more detailed information about server operations.

Motivation

The MapGuide Server is a very complicated application and the current logs provide insufficient detail to determine the root cause of issues on production servers. The proposed functionality enhances the core framework so that additional logging information can be added over a period time.

Proposed Solution

Implement a classification system for log details controlled by a LogsDetail parameter in serverconfig.ini:

[GeneralProperties]
LogsDetail = ResourceService:0,FeatureService:1,RenderingService:2,MappingService:3

The per-service classification scheme is defined as follows:

• Level 0 - Errors
  • Errors (exceptions) are logged without method parameters for the specified service
• Level 1 - Warnings and Errors
• Level 2 - Trace, Warnings, and Errors
• Level 3 - Internal Trace, Trace, Warnings, and Errors

Implications

Test Plan

Funding/Resources

Autodesk