You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actually everytime the usagelog.log is sended to the Pimcore Team, the file is deleted.
The content of this file is great to retrieve which user make which action if needed.
I think it should be keeped zipped on the server and not being unlink like it is done actually. Please see: https://github.com/pimcore/pimcore/blob/master/pimcore/lib/Pimcore/Log/Maintenance.php#L140
Actually on a project we wanted to consult this log and it was just flushed and deleted some hours ago... as we wanted to get yesterday information, we lost them : (
The only way to prevent this seems to desactivate the submission for now.
Thanks!
The text was updated successfully, but these errors were encountered:
We can see here that the only way to keep usagelog is to disable usage sending (so return line 96 is executed) if we do not want to lost recent usage log (sending is based on the number of line, not on the time like the log cleaning on line 140).
A solution will be: change sending to time based criteria (30 days old for instance) wich involve file rotation (archive of this file). So at least we are sure at each time to be able to check usages 30 days back.
Another solution is simply not delete it (like if sending to pimcore checkbox was not cheked).
Actually everytime the usagelog.log is sended to the Pimcore Team, the file is deleted.
The content of this file is great to retrieve which user make which action if needed.
I think it should be keeped zipped on the server and not being unlink like it is done actually. Please see:
https://github.com/pimcore/pimcore/blob/master/pimcore/lib/Pimcore/Log/Maintenance.php#L140
Actually on a project we wanted to consult this log and it was just flushed and deleted some hours ago... as we wanted to get yesterday information, we lost them : (
The only way to prevent this seems to desactivate the submission for now.
Thanks!
The text was updated successfully, but these errors were encountered: