@lzap hello!!! thanks for chiming in. I found a workaround, while not elegant, seems to be doing the job. Frankly I don’t care about that level of detail in the production.log from ruby, so I just disabled the app log in settings.yaml. I know the information might be important, but if you aren’t going to let me as an administrator manage it, and it consumes as much space as it does, I’ll just disable the logging until there’s a reason for it.
I had noticed a couple of large JSON data loads. One in particular was SCAP content reporting. the contents of the SCAP report would be displayed in the production.log as JSON. Obviously this was a huge amount of data and causing problems for space.
We have since disabled SCAP reporting, as we’re moving to utilizing another tool, so that logging is really no longer an issue.
I have to agree with you on the logging level. This should be customizable in all aspects by the customer.