<p dir="auto">When root logger hijacking is disabled, it feels rather inappropriate to change the log level of the root logger...</p>
<p dir="auto">Hi there,</p>
<p dir="auto">I'm experiencing an issue similar to <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="32412527" data-permission-text="Title is private" data-url="https://github.com/celery/celery/issues/2016" data-hovercard-type="pull_request" data-hovercard-url="/celery/celery/pull/2016/hovercard" href="https://github.com/celery/celery/pull/2016">#2016</a>, <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="27362729" data-permission-text="Title is private" data-url="https://github.com/celery/celery/issues/1867" data-hovercard-type="issue" data-hovercard-url="/celery/celery/issues/1867/hovercard" href="https://github.com/celery/celery/issues/1867">#1867</a>, in that celery still hijacks the root logger despite setting <code class="notranslate">CELERYD_HIJACK_ROOT_LOGGER</code> to False (as read from <a href="http://celery.readthedocs.org/en/latest/configuration.html#celeryd-hijack-root-logger" rel="nofollow">http://celery.readthedocs.org/en/latest/configuration.html#celeryd-hijack-root-logger</a>). I use celery + Django for several projects and except for this wart, it's fantastic. What I really, really, need is a way to configure celery so that it does not attempt to configure logging <em>at all</em>. It's quite frustrating to try and work out why our custom crafted logging configuration works as expected for our web servers, but is completely wiped out for our task code - only to realize that celery itself is blowing away our logging configuration.</p>
<p dir="auto">In reading the previous issues related to this I seems that you are understandably reluctant to change the current behaviour of <code class="notranslate">CELERYD_HIJACK_ROOT_LOGGER</code> for compatibility reasons. Would you be open to a new setting? Something like <code class="notranslate">CELERYD_CONFIGURE_LOGGING=False</code>, that would cause celery to not attempt to configure logging at all. If you are open to it I'd be happy to contribute a PR with tests.</p>
<p dir="auto">Thanks!</p>