Mailing-List: contact dev-help@aurora.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CANyrgvfXGNWbzq4XTF+2fcm2S=-vrAR-ZE8j4t+-kigXj0s5Yw@mail.gmail.com>
References: 
 <CAFWq12U6w+p7TZDGS5VtCEVxA+PxiXgxUa_vxn9x5wqsaqAdHA@mail.gmail.com>
	<CAMReA91WLoy33SHBk7w3Gzs7jYQFVpzuiQpCAsWaEe_viwYm8Q@mail.gmail.com>
	<CAFWq12XRX=4HLfDG1tGi447gJafHgz6Vws8Nd-DRsfrNB=PUGw@mail.gmail.com>
	<CAMReA90aePV-bTsSDo5zE9hYbRL_qQzK4Be0iyhXcxekxXuuyA@mail.gmail.com>
	<CANyrgvfXGNWbzq4XTF+2fcm2S=-vrAR-ZE8j4t+-kigXj0s5Yw@mail.gmail.com>
Date: Tue, 29 Dec 2015 20:47:17 -0800
Message-ID: 
 <CAFWq12XAxYS-_hTtO1-LkHowdjoCNrFRixWyo0nJfUTDuJ+jJA@mail.gmail.com>
Subject: Re: [PROPOSAL] Use standard logging practices
From: Bill Farner <wfarner@apache.org>
To: dev@aurora.apache.org, Jake Farrell <jfarrell@apache.org>
Content-Type: multipart/alternative; boundary=089e013a2132990c5e0528163b66

--089e013a2132990c5e0528163b66
Content-Type: text/plain; charset=UTF-8

Aha, good catch.  Sounds like log4j takes the cake.

On Tue, Dec 29, 2015 at 7:34 PM, Jake Farrell <jfarrell@apache.org> wrote:

> Logback can not be used as it is LGPL licensed
>
> -Jake
>
> On Tue, Dec 29, 2015 at 7:02 PM, Jeff Schroeder <
> jeffschroeder@computer.org>
> wrote:
>
> > Primarily it is faster, uses less memory, and annotates tracebacks with
> > package versions. The last one seems like a winner for debugging user
> > issues or operationally.
> >
> > http://logback.qos.ch/reasonsToSwitch.html
> >
> > I'm not strongly opinionated either way, but it does seem like a better
> > log4j.
> >
> > On Tuesday, December 29, 2015, Bill Farner <wfarner@apache.org> wrote:
> >
> > > I don't have a strong opinion about logback vs log4j.  Can you
> summarize
> > > some of the tradeoffs?
> > >
> > > On Tue, Dec 29, 2015 at 3:52 PM, Jeff Schroeder <
> > > jeffschroeder@computer.org <javascript:;>>
> > > wrote:
> > >
> > > > What about using logback instead of log4j? It has some interesting
> > > benefits
> > > > over log4j and we wouldn't be the first large mesos framework to
> switch
> > > to
> > > > it.
> > > >
> > > > Personally, I'd love to see glog burn and die in a fire.
> > > >
> > > > On Monday, December 28, 2015, Bill Farner <wfarner@apache.org
> > > <javascript:;>> wrote:
> > > >
> > > > > We're currently using some logging scaffolding carried over from
> > > Twitter
> > > > > commons.  I would like to propose that we dismantle some of this in
> > > favor
> > > > > of more standard java application logging conventions.
> > > > >
> > > > > Concretely, i propose we remove the following scheduler command
> line
> > > > > arguments:
> > > > > -logtostderr
> > > > > -alsologtostderr
> > > > > -vlog
> > > > > -vmodule
> > > > > -use_glog_formatter
> > > > >
> > > > > Instead of these, we can allow users to customize logging via
> > standard
> > > > > java.util.logging inputs (e.g. logging.properties).  We could
> explore
> > > > using
> > > > > an alternative to java.util.logging, but i suggest we retain that
> > > backend
> > > > > for now (since it's what we're currently using).
> > > > >
> > > >
> > > >
> > > > --
> > > > Text by Jeff, typos by iPhone
> > > >
> > >
> >
> >
> > --
> > Text by Jeff, typos by iPhone
> >
>

--089e013a2132990c5e0528163b66--