Improve error warning log pollution + composer recipes (Part 3)

[melroy89]

• Recipe updates (doctrine-migrations-bundle, flystem-bundle, monolog-bundle, stimulus-bundle, translation)
• Enable log rotation on production (max 7 files, one per dag)
• Enable log rotation in development mode as well (max 10 files)
• Full stacktraces in development mode, strict logging on action level, buffer size, and deprecation to stderr
• Change default development log level from debug to info, with a remark the developer can always enable debug. Warning: debug is very very verbose, hence info as default.

[ghost]

I got this info/warning during the migration step, is this expected?

[2023-10-24T13:27:10.041008+00:00] deprecation.INFO: User Deprecated: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the "reportFieldsWhereDeclared" constructor parameter to true. (AttributeDriver.php:78 called by App_KernelProdContainer.php:530, https://github.com/doctrine/orm/pull/10455, package doctrine/orm) {"exception":"[object] (ErrorException(code: 0): User Deprecated: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the \"reportFieldsWhereDeclared\" constructor parameter to true. (AttributeDriver.php:78 called by App_KernelProdContainer.php:530, https://github.com/doctrine/orm/pull/10455, package doctrine/orm) at /var/www/kbin/vendor/doctrine/deprecations/lib/Doctrine/Deprecations/Deprecation.php:210)"} []

[ghost]

Also, my prod log file is already at 40M about a second after updating and growing about 1 MB every second...lol.

[melroy89]

Ps. Sorry about 30 commits. I can rewrite git history if you wish. Then again we will use squash merge so it will be a single commit anyway..

[melroy89]

Also, my prod log file is already at 40M about a second after updating and growing about 1 MB every second...lol.

Ow that is maybe not cool.. I did enable log rotation. But it shouldn't spam that much to prod.log. Dev.log is a different story of course. Let me check

[melroy89]

I got this info/warning during the migration step, is this expected?

[2023-10-24T13:27:10.041008+00:00] deprecation.INFO: User Deprecated: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the "reportFieldsWhereDeclared" constructor parameter to true. (AttributeDriver.php:78 called by App_KernelProdContainer.php:530, https://github.com/doctrine/orm/pull/10455, package doctrine/orm) {"exception":"[object] (ErrorException(code: 0): User Deprecated: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the \"reportFieldsWhereDeclared\" constructor parameter to true. (AttributeDriver.php:78 called by App_KernelProdContainer.php:530, https://github.com/doctrine/orm/pull/10455, package doctrine/orm) at /var/www/kbin/vendor/doctrine/deprecations/lib/Doctrine/Deprecations/Deprecation.php:210)"} []

Is the deprecation message pointing to a file in our code base? I don't think so?

[asdfzdfj]

Also, my prod log file is already at 40M about a second after updating and growing about 1 MB every second...lol.

Ow that is maybe not cool.. I did enable log rotation. But it shouldn't spam that much to prod.log. Dev.log is a different story of course. Let me check

it looks like you also axed fingers_crossed log type in the process (from my understanding it would only print out logs when message with higher configured severity appears, along with some previous log lines for context)

so now it would just log all that's enabled

[ghost]

I got this info/warning during the migration step, is this expected?

[2023-10-24T13:27:10.041008+00:00] deprecation.INFO: User Deprecated: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the "reportFieldsWhereDeclared" constructor parameter to true. (AttributeDriver.php:78 called by App_KernelProdContainer.php:530, https://github.com/doctrine/orm/pull/10455, package doctrine/orm) {"exception":"[object] (ErrorException(code: 0): User Deprecated: In ORM 3.0, the AttributeDriver will report fields for the classes where they are declared. This may uncover invalid mapping configurations. To opt into the new mode today, set the \"reportFieldsWhereDeclared\" constructor parameter to true. (AttributeDriver.php:78 called by App_KernelProdContainer.php:530, https://github.com/doctrine/orm/pull/10455, package doctrine/orm) at /var/www/kbin/vendor/doctrine/deprecations/lib/Doctrine/Deprecations/Deprecation.php:210)"} []

Is the deprecation message pointing to a file in our code base? I don't think so?

Good point... just pointing out the obvious if you will. Doesn't bother me if it doesn't bother you.

[melroy89]

it looks like you also axed fingers_crossed log type in the process (from my understanding it would only print out logs when message with higher configured severity appears, along with some previous log lines for context)

so now it would just log all that's enabled

It was not very well documented on https://symfony.com/doc/current/logging.html#how-to-rotate-your-log-files, but we now use rotating_file in the nested section. Resolving the issue big files due to rotating_files in the main section of production. But instead of type stream in dev, I now use the rotating_files type in the main section of the development config.

This last config allows people to run development mode on a federated instance without worrying to get a 100GB dev.log files (I have been there.. done that 😢 ).

[asdfzdfj]

I don't think I see anything particularly standing out, and all seems to be looking fine. @nobodyatroot ?

[ghost]

Much better, no more exploding logfile size!

[melroy89]

Much better, no more exploding logfile size!

sorry about that ^^ I made it worse instead of better. But now it should be even better than before.