collector debug log usage controls

I have encountered far too many cases now where logging implemented within official logicmodules (typically configsources) blows out the disk.  Given LM installation recommendations (https://www.logicmonitor.com/support/getting-started/i-just-signed-up-for-logicmonitor-now-what/3-adding-collectors/), this situation is very dangerous.  I would expect to be kicked out of a client if one of those log blowups filled the disk on a non-dedicated server holding a collector.  Please ensure that can never happen -- all disk logging should be required to be marshaled through a subsystem that disallows storing more than a preset amount of data, preferably configurable at the collector level.  Alternatively, log to the SaaS platform, not to local disk.