Log flooded with spooler messages from the blotter

Technical Help
#1

Does anyone else have an issue with the log being flooded with these spooler messages when running the detailed log? command: # quantrocket flightlog stream --detail
Same messages can be seen directly in the container with # docker logs -f quantrocket_blotter_1
Restarting the container doesn't appear to make a difference.

quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_7_2_1682991338_1531905572_318385 
quantrocket_blotter_1|[spooler /var/tmp/uwsgi/spool pid: 12] managing request uwsgi_spoolfile_on_3ce4ee4359c2_6_2_1743043062_1531903145_349511
#2

This is the blotter polling for new executions. You can silence the logging by passing an environment variable to the container:

blotter:
  image: 'quantrocket/blotter:x.x.x'
  environment:
    UWSGI_SPOOLER_QUIET: 'true'
#3

Okay, so it's nothing to worry about it's common and should just be silenced? I actually thought it might have been the messages from the history container there was acting up. Maybe other containers as well. I'm not getting as many messages in the detailed flight log as I used to. Fx. to see what the history container is pulling from IB I need to run the docker log command to see them directly on the container.
docker logs -f -t quantrocket_history_1.