+1 Could we still keep the Glog formatter class so folks who want to have the same log formatting between the Aurora log lines and the Mesos driver (which prints to stderr by default) just have to add a line to their logging.properties?
The alternative means users would have to build their own glog formatter and add it to the classpath in addition to setting the formatter in logging.properties which is not straight forward if you want to have reasonably formatted log entries between the driver and the scheduler. On Mon, Dec 28, 2015 at 2:54 PM, Bill Farner <wfar...@apache.org> 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). > > -- > Zameer Manji > >
