Keeping php error log around

CloudyBlake

So I don't know how but a php error log finally showed up in the website I've been working. I was going to look at it in depth, but I went to change php version and the log file gets wiped.

This should be kept around or give us a setting to control the behavior.

8Dweb

I think I will jump in... I agree. This inability to see live logs apart from command line, and then it rolls on you is driving us crazy as we continue to migrate sites into Enhance.

I really hope a better log system is headed our way, with full log view/live log view from the interface. This one thing was something I should have thought out in much greater detail.

In any case, Adam and the team have been AWESOME when we could not figure it out, and in nearly all cases quickly pointed out the problem or given excellent suggestions.

CloudyBlake

8Dweb
Yeah, I'm not a fan of the current logs, they need more detail or more events. (meaning the logs in the UI)

AdamR

Very much agree. Logging in Enhance makes it very difficult to troubleshoot issues.

The issues I have seen are:

Retention: There is no retention. Historical logs need to be stored for a certain period (both error logs and access logs), maybe with a setting in the panel where you can decide to keep them for 'X' number of days. Access logs are also extremely limited (less than 24 hours in most cases I have seen).

PHP Container restarts: Error logs get wiped out when a PHP container restarts, this is a problem.

Accessibility: It is nice that you can view the error log through the File Manager, but access logs can only be viewed through command line which is really annoying trying to track anything down. You should be able to quickly download the logs (or a zip of historical logs) in the UI, so you can quickly and easily parse them on your local machine.