Comment 1 for bug 1456957

So while this is potentially a problem in old versions of Juju, we're moving away from using rsyslog to do the aggregation. With direct connections our queue is just in-memory, and thus we won't fill disk and we already drop messages when full.
When we switch to logging via the API (to the DB) we again won't end up with large rsyslog disk queues.

A healthy environment won't run into this, it was more about preventative measures against failure cascading (we fail to log, causing us to fill up disk, causing other failures, etc.)

We already have the 0.5GB max queue disk space in place, which means this won't every get crazily out of hand.