Opened 9 years ago
Last modified 9 years ago
#1048 closed defect
eassylogging log format — at Version 1
Reported by: | George Merticariu | Owned by: | Vlad Zamfir |
---|---|---|---|
Priority: | major | Milestone: | 9.1.x |
Component: | rasserver | Version: | development |
Keywords: | Cc: | Dimitar Misev, Alex Dumitru, Vlad Merticariu, Alex Toader | |
Complexity: | Medium |
Description (last modified by )
Now that we have eassylogging integrated in rasdaman we should proceed in increasing the quality of the log files. Below is the initial plan on how the logging config should be.
Each component should have it's own configuration file. In order to minimize the number of config files we can reduce the to two files:
a) client logging - rasql, directql, other clients.
b) server logging - rasserver, rasmgr
Client logging:
- prints to console (i.e. outstream)
- Format: "%level - %msg"
- Levels: Fatal, Error, Warning, Info
Server logging:
- prints to file
- Format: "%level - %datetime, %loc, %func: %msg"
- Levels: Fatal, Error, Warning, Info, (conditional) Debug, (conditional) Trace
The files should be created in <rasdaman_inst>/etc and should be used to configure the loggers on runtime.
Change History (1)
comment:1 by , 9 years ago
Component: | undecided → rasserver |
---|---|
Description: | modified (diff) |
Milestone: | → 9.1.x |
Note:
See TracTickets
for help on using tickets.