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
We store a copy of production.log files from the last 4 releases, which should normally ensure that we have 30 days worth of records.
But it seems that logs can be truncated during the week if they get too large, so we have gaps in logs. Sometimes after only a couple of days (while we still have logs from a point in time 4 weeks ago).
Possible Fix
Maybe we can increase the truncate limit to reduce the likelihood of gaps.
Or better, move logging to the shared folder (like we already do for puma logs) so that we don't have gaps. We can set a reasonably high limit to allow for hopefully 30 days
The text was updated successfully, but these errors were encountered:
Description
We store a copy of
production.log
files from the last 4 releases, which should normally ensure that we have 30 days worth of records.But it seems that logs can be truncated during the week if they get too large, so we have gaps in logs. Sometimes after only a couple of days (while we still have logs from a point in time 4 weeks ago).
Possible Fix
Maybe we can increase the truncate limit to reduce the likelihood of gaps.
Or better, move logging to the shared folder (like we already do for puma logs) so that we don't have gaps. We can set a reasonably high limit to allow for hopefully 30 days
The text was updated successfully, but these errors were encountered: