logspout
logspout copied to clipboard
gliderlabs
Logspout drops the first few lines if nothing has been logged for a while
We recently upgraded to Logspout v3.2 from v2, and many things are better.
We have it running on a machine which runs jobs on cron twice a day. We noticed that the log entries for these jobs, which are usually only a few lines long, were truncated from the top or missing altogether when we used v3.2. Subsequent jobs, if run within a few minutes, are not missing any initial lines.
From https://github.com/gliderlabs/logspout/issues/309#issuecomment-306818766 I see that logspout is expected to drop logs while it is reconnecting, and we do see the reconnect successful message immediately before the truncated logs.
Is there anything we can do to mitigate this?
It looks like there are some suggestions in that thread you linked. The best thing would be to fix the issue in some way. I'm open to suggestions but even more would love to see someone jump in and take on the work. Unfortunately my $DAY_JOB is taking up all my coding time.
@michaelshobbs Thank you for your reply. I'm afraid I have no Go so I'm not going to be much use on the code in the foreseeable future, but if I find out anything interesting I will bring it back here.