1

I've got a Craft CMS installation that is set to production mode. I notice that my logs get flooded with a bunch of entries which don't seem very useful.

For example, in a matter of several days, I've already got console.log up to console.log.5 - So it's rotated the log file 5 times already. These files are filled with what seems like every single query that gets executed on the website. They're 70k lines a piece. It also logs a lot of entries in queue.log, among other files.

How can I stop logging information and only log things which require my attention, such as errors?

Thanks!

|improve this question
  • Are you sure you don't have devMode enabled in production? docs.craftcms.com/v3/config/config-settings.html#devmode – Brad Bell Oct 27 '18 at 21:42
  • My .env file is set to "production", and in config/general.php I'm don't have any devMode item in the production array. The linked documentation says the default value is false - so I would assume it should be false. – Tyler Oct 27 '18 at 23:43
1

As someone who theoretically might inherit your site one day... and also as future-you trying to diagnose a problem... please don't try to limit what Craft logs. If you want a quicker way to look for critical problems, check out the Yii2 Debug Toolbar as discussed here Profiling your Website with Craft CMS 3’s Debug Toolbar

You can use it to very quickly and easily see only errors, or only warnings, and so on. And then if the additional data that Craft logs is needed to help you diagnose a problem, it'll still be there.

I echo Brad's comments, though, unless for some reason devMode is on, it shouldn't be logging every query, except for performance profiling.

|improve this answer
0

This will be a similar answer as here: Craft 3 large log file sizes

Basically Craft goes with Yii's default FileTarget settings, which is 5 log files of 10MB each before they start rotating out. Those are individual limits for both web.log and console.log files.

If you want to change those behaviors you'll need to modify those properties via a config/app.php file using your own FileTarget settings.

There's another post here with some useful guidance: Craft 3 plugins - Logging in a separate *.log file

|improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.