FEEDBACK REQUESTED: GlassFish 4.0 logging verbosity
At the JavaOne GlassFish Community meeting in 2011 and 2012, one of the suggested improvements was to improve GlassFish logging. To paraphrase, "The logs are too hard to read and track what is happening". As we continue engineering GlassFish 4.0, we would like to better understand what would best help developers as it relates to logging.
To make this as "open ended" as possible, how can we improve GlassFish logging during the development process?