[Geoserver-devel] Improving the logging situation

Hi all,

I have been working on fixing the followign jira issue:

http://jira.codehaus.org/browse/GEOS-898

Which involves startup logging once again becoming very cluttered. I
dont really think that just one-upping what our current startup is
logged at is really all that acceptable and will work long term. There
are also some other issues which it will not solve. So I have created a
GSIP to try to improve our logging situation.

http://docs.codehaus.org/display/GEOS/GSIP+13+-+Logging

I have tried to specify what I beleive the current limitations and
problems are and proposed a solution. Please feel free to comment /
complain / call my crazy. And if you think there are some other
limitations that have not been addressed please add them.

-Justin

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org

Justin Deoliveira ha scritto:

Hi all,

I have been working on fixing the followign jira issue:

http://jira.codehaus.org/browse/GEOS-898

Which involves startup logging once again becoming very cluttered. I
dont really think that just one-upping what our current startup is
logged at is really all that acceptable and will work long term. There
are also some other issues which it will not solve. So I have created a
GSIP to try to improve our logging situation.

http://docs.codehaus.org/display/GEOS/GSIP+13+-+Logging

I have tried to specify what I beleive the current limitations and
problems are and proposed a solution. Please feel free to comment /
complain / call my crazy.

Crazy!!! :slight_smile: (happy now?)
Seriously, I agree with most of what you stated/proposed
minus a few details:
* log configuration file should be put in the data directory, for the
   user to modify, and possibly have a way to reload it (with log file
   templates put in the classpath ready to be extracted in the data dir
   if missing)
* instead of having fixed rules on log levels, let's ship with a small
   set of pre-configured log configurations, and have the user choose
   which one he would like to use (production, geoserver debug, full
   debug). If the user feel like adding its own, we can list that one
   too.

How does this sound?
Cheers
Andrea

Andrea Aime wrote:

Justin Deoliveira ha scritto:

Hi all,

I have been working on fixing the followign jira issue:

http://jira.codehaus.org/browse/GEOS-898

Which involves startup logging once again becoming very cluttered. I
dont really think that just one-upping what our current startup is
logged at is really all that acceptable and will work long term. There
are also some other issues which it will not solve. So I have created a
GSIP to try to improve our logging situation.

http://docs.codehaus.org/display/GEOS/GSIP+13+-+Logging

I have tried to specify what I beleive the current limitations and
problems are and proposed a solution. Please feel free to comment /
complain / call my crazy.

Crazy!!! :slight_smile: (happy now?)
Seriously, I agree with most of what you stated/proposed
minus a few details:
* log configuration file should be put in the data directory, for the
   user to modify, and possibly have a way to reload it (with log file
   templates put in the classpath ready to be extracted in the data dir
   if missing)

Works for me. We could fire off a reload when the user presses the
loadFromXml button.

* instead of having fixed rules on log levels, let's ship with a small
   set of pre-configured log configurations, and have the user choose
   which one he would like to use (production, geoserver debug, full
   debug). If the user feel like adding its own, we can list that one
   too.

Good idea. I like this too.

How does this sound?

Great, I am going to add your feedback to the page.

Cheers
Andrea

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:1004,45f658a9317161425493344!

--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org