Improve usability of message logs.

[GoogleCodeExporter]

1. To which tool/application/daemon will this feature apply?

Tungsten Replicator. 

2. Describe the feature in general

Tungsten message logs are difficult to read, as they include detailed messages 
of interest largely to developers and are poorly structured for basic problem 
diagnosis.  Logs will be cleaned up as follows: 

a. Message log location will be configurable to allow placement of logs in 
standard locations like /var/log/tungsten. 

b. Messages will be split into a detailed diagnostic log and a much shorter 
user log containing only major events (such as going online or failing due to 
an error). 

c. Messages will clearly indicate the replication service to which they belong. 
 Logs will be divided for each service. 

d. Errors will show a clearly message indicating the cause of the problem (if 
known).  SQL failures will if possible indicate the failing SQL command. 

3. Describe the feature interface

This is mainly internal clean-up.  There may also be some restructuring of the 
default log4j.properties file. 

4. Give an idea (if applicable) of a possible implementation

Internal cleanup of log messages and exception handling. 

5. Describe pros and cons of this feature.

5a. Why the world will be a better place with this feature.

The biggest improvement is that users should be able to determine the cause of 
most errors without looking at the log. 

5b. What hardship will the human race have to endure if this feature is
implemented.

Exception handling in particular is brittle.  It is likely clean-up will 
trigger a few bugs.  

6. Notes

Original issue reported on code.google.com by berkeley...@gmail.com on 3 Jul 2011 at 11:39

[GoogleCodeExporter]

Original comment by Steph.Giron on 25 Jul 2011 at 8:55

[GoogleCodeExporter]

This is reasonably complete for now.  Further improvements in logging will be 
handled on a case-by-case basis.  For now logs are not divided by service. 

Original comment by robert.h...@continuent.com on 24 Nov 2011 at 6:19

• Added labels: FixedIn-2.0.5
• Removed labels: FixedIn-2.0.6

[GoogleCodeExporter]

Original comment by robert.h...@continuent.com on 28 Nov 2011 at 6:45

• Changed state: Fixed