Hm... am I the only one who finds it useless to have all hawkular components on DEBUG even when developing? Too much data to see anything useful. If there is no significant and immediate opposition against this, I'll have to introduce a separate standalone-dev.xml where DEBUG can be kept for all, but it has to be set back to INFO or even WARN in standalone-itest.xml because DEBUGging all makes the log size exceed Travis limit of 4MB. -- P On 2015-05-28 21:13, John Mazzitelli wrote: > I created a JIRA [1] and PR [2] so that when we build a dev build > you'll get the console to show DEBUG log messages. In production > mode, it stays at INFO level. I also added additional logging > categories - double check that I added your component's logger > categories correctly. In addition, I removed xsl:if checks and > changed to xsl:choose in the .xsl. > > Merge at your earliest convenience, please :) > > [1] https://issues.jboss.org/browse/HWKINVENT-55 [2] > https://github.com/hawkular/hawkular/pull/149 > _______________________________________________ hawkular-dev mailing > list hawkular-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev >

On 2015-05-28 22:28, John Mazzitelli wrote: > I only put them all at DEBUG only because its a dev build so I > figured why not. Travis has said clearly why not. > If its too noisy, we can put them at INFO out of box. I do want at > least the categories listed, so devs can easily go in and turn on and > off debug for their particular components of interest. Yes, that is a good idea. > I've been > doing this by hand and its annoying, so that's why its in the dev > build now. > > The CONSOLE needs to be at DEBUG because without that, it doesn't > matter what you do to the individual categories, the debug messages > get eaten up. changing the CONSOLE level to DEBUG was just yet > another thing I had to remember to change manually, so again that is > why its in the dev build. Leave that at DEBUG, but the individual > components at INFO could be a good middle-ground configuration. +1 would you please do that, so that Travis stops complaining about the 4MB limit? Thanks, Peter > > ----- Original Message ----- >> Hm... am I the only one who finds it useless to have all hawkular >> components on DEBUG even when developing? Too much data to see >> anything useful. >> >> If there is no significant and immediate opposition against this, >> I'll have to introduce a separate standalone-dev.xml where DEBUG >> can be kept for all, but it has to be set back to INFO or even WARN >> in standalone-itest.xml because DEBUGging all makes the log size >> exceed Travis limit of 4MB. >> >> -- P >> >> >> On 2015-05-28 21:13, John Mazzitelli wrote: >>> I created a JIRA [1] and PR [2] so that when we build a dev >>> build you'll get the console to show DEBUG log messages. In >>> production mode, it stays at INFO level. I also added additional >>> logging categories - double check that I added your component's >>> logger categories correctly. In addition, I removed xsl:if checks >>> and changed to xsl:choose in the .xsl. >>> >>> Merge at your earliest convenience, please :) >>> >>> [1] https://issues.jboss.org/browse/HWKINVENT-55 [2] >>> https://github.com/hawkular/hawkular/pull/149 >>> _______________________________________________ hawkular-dev >>> mailing list hawkular-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >> >>

On 28 May 2015, at 22:28, John Mazzitelli wrote: > The CONSOLE needs to be at DEBUG because without that, it doesn't > matter what you do to the individual categories, the debug messages > get eaten up. changing the CONSOLE level to DEBUG was just yet Could we put the DEBUG level only for the *log file* (and make it wrap over only at large log sizes) and keep the (stdout) console at INFO level? _______________________________________________ hawkular-dev mailing list hawkular-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev