RE: Avoid overloading sugarcrm.log by channelling logs

Frédéric Rinaldi — Mon, 07 Nov 2022 08:10:44 GMT

Hi [mention:7b9c65d787144b25aa14d4e63cda83c1:e9ed411860ed4f2ba0265705b8793d05],

thank you for this usefull solution.

I have a related question : what is the best solution to be warned when a fatal error happened (instead of having to check the logs every days etc.) ? Of course we can imagine using a log checker solution, but it's not compliant with several of our customer expectation, nor with cloud solution.

So would it be to customized the core logger to, for instance, send an email when a fatal error happened ? Or log an activity in Sugar ?

Any idea is welcome.

Fred

RE: Avoid overloading sugarcrm.log by channelling logs

Enes Saridogan — Fri, 09 Sep 2022 07:35:04 GMT

Hi [mention:7b9c65d787144b25aa14d4e63cda83c1:e9ed411860ed4f2ba0265705b8793d05],

Thanks for the trick, it would be useful on huge instances while we can separate for the jobs, hooks, etc ... and leaving the sugarcrm.log for the "high level" logs.

Have a nice week-end !

Best regards,

Enes