title: Why does celery.control.inspect report fewer queued tasks than rabbitmqctl?
body: <p><code>rabbitmqctl</code> correctly reports thousands of queued tasks:</p>
  
  <pre><code>$ sudo rabbitmqctl -q list_queues name messages messages_ready messages_unacknowledged
  default 13142   13126   16
  </code></pre>
  
  <p>Yet celery reports:</p>
  
  <pre><code>&gt;&gt;&gt; len(app.control.inspect().active()['celery@default'])
  4
  &gt;&gt;&gt; len(app.control.inspect().scheduled()['celery@default'])
  1
  &gt;&gt;&gt; len(app.control.inspect().reserved()['celery@default'])
  16
  &gt;&gt;&gt; len(app.control.inspect().revoked()['celery@default'])
  0
  </code></pre>
  
  <p>The correct number (thousands) of tasks seem to show up in <code>app.control.inspect().stats()['celery@default']['total']</code>, but I really want to know the correct number of <em>outstanding</em> queued tasks from within python, and <code>active()</code> et al seem to only ever report up to 16 or so -- perhaps there is a limit?</p>
  
  <p>Short of using privileged subprocess calls to <code>rabbitmqctl</code>, how can I get the full queued task count from within python, preferably via <code>celery</code> (btw this server is using Celery 3.1.8 currently)</p>