[stats_logger] entries flooding the console log

[rumbin]

Make sure these boxes are checked before submitting your issue - thank you!

• I have checked the superset logs for python stacktraces and included it here as text if any
• I have reproduced the issue with at least the latest released version of superset
• I have checked the issue tracker for the same issue and I haven't found one similar

Superset version

0.20.4

Expected results

The console log of superset runserver shows useful information.

Actual results

The console output is flooded with these messages:

2017-10-12 17:28:23,111:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:23,363:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:24,111:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:25,111:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:25,362:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:26,111:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:27,111:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:27,362:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:28,112:INFO:root:[stats_logger] (incr) queries
2017-10-12 17:28:29,113:INFO:root:[stats_logger] (incr) queries

Steps to reproduce

Run superset runserver in the foreground.
Maybe it's important that we are running superset worker parallel and use redis as backend/cache.

Thoughts

Did I simply miss any config option to silence these messages?
Parts of my config that I consider as being somewhat related:

# Whether to run the web server in debug mode or not
DEBUG = False
# Whether to show the stacktrace on 500 error
SHOW_STACKTRACE = True
# Console Log Settings
LOG_FORMAT = '%(asctime)s:%(levelname)s:%(name)s:%(message)s'
LOG_LEVEL = 'DEBUG'
# Whether to bump the logging level to ERRROR on the flask_appbiulder package
# Set to False if/when debugging FAB related issues like
# permission management
SILENCE_FAB = True

[xrmx]

They should probably be at debug and not at info level

[mistercrunch]

Thanks for reporting this, here's the fix:
#3662

[wutengyue]

I also encountered this problem, so, LOG_LEVEL = what? @mistercrunch