HomeMesosphereNo notifications. 4 unresolved issues.

Turn off debug for jetty
ClosedAll Users

Authored by timcharper on Dec 8 2016, 10:02 PM.

Details

Summary

The debug logs for jetty are almost never helpful; this reduces noise
significantly when turning on marathon debug logging.

Test Plan

n/a

Diff Detail

Repository
rMARATHON marathon
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.
timcharper retitled this revision from to Turn off debug for jetty.Dec 8 2016, 10:02 PM
timcharper updated this object.
timcharper edited the test plan for this revision. (Show Details)
jdef accepted this revision.Dec 8 2016, 11:55 PM
This revision is now accepted and ready to land.Dec 8 2016, 11:55 PM
jasongilanfarr requested changes to this revision.Dec 9 2016, 12:33 AM

This should have no effect at all. The root logger is at info, so how is this any different?

This revision now requires changes to proceed.Dec 9 2016, 12:33 AM

when the logging_level flag is set to DEBUG that changes the default logging to DEBUG but the other levels that have overrides stay that way .. yes?

Well that's confusing.

This revision is now accepted and ready to land.Dec 9 2016, 12:42 AM
jdef added a comment.Dec 9 2016, 12:43 AM

when the logging_level flag is set to DEBUG that changes the default
logging to DEBUG but the other levels that have overrides stay that way ..
yes?

This indeed does change things. logging_level modifies the root logging level. The override prevents worthless / noisy messages from cluttering the log.

This revision was automatically updated to reflect the committed changes.