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
This should mean that logs should rotate every Sunday at midnight. However I think I am generating more logs than 50M every day. So log rotation happens every few hours. But I have just one log file generated per day which upon inspection does not contain entire day logs. I am losing logs here in PRODUCTION which is quite critical. Expected behavior is that log file name append something at the end like log__2019-09-05-1.log, log__2019-09-05-2.log if a log file named log__2019-09-05.log already exists.
I really think this should be documented better. By not having this what you really want the devs to do is that figure how much size of logs I am generating, and after that configure logrotate module in a way that no logs are lost.
Please help me if my understanding is wrong.
The text was updated successfully, but these errors were encountered:
Here's my config:
rotateInterval │ 0 0 0 * * 0
dateFormat │ YYYY-MM-DD
max_size │ 50M
This should mean that logs should rotate every Sunday at midnight. However I think I am generating more logs than 50M every day. So log rotation happens every few hours. But I have just one log file generated per day which upon inspection does not contain entire day logs. I am losing logs here in PRODUCTION which is quite critical. Expected behavior is that log file name append something at the end like log__2019-09-05-1.log, log__2019-09-05-2.log if a log file named log__2019-09-05.log already exists.
I really think this should be documented better. By not having this what you really want the devs to do is that figure how much size of logs I am generating, and after that configure logrotate module in a way that no logs are lost.
Please help me if my understanding is wrong.
The text was updated successfully, but these errors were encountered: