Currently the line limit for log files is hardcoded to 5'000, somewhat restrictive for many use cases.
The reason for this is outlined in #421
As a workaround for use cases where the end of the file if of interest (probably the majority of use cases!), we should investigate an option to serve the last 5'000 lines rather than the first.
This would work by tailing the log file starting X lines from the end of the file, continuing for Y lines.
The current limit is 5'000, so we could try, X=2'500 and Y=2'500.
However, most of the issue with log files is the loading time rather than the streaming time, so we could also entertain X=5'000 and Y=5'000 (which would have the same impact on load as the status quo).
Currently the line limit for log files is hardcoded to 5'000, somewhat restrictive for many use cases.
The reason for this is outlined in #421
As a workaround for use cases where the end of the file if of interest (probably the majority of use cases!), we should investigate an option to serve the last 5'000 lines rather than the first.
This would work by tailing the log file starting X lines from the end of the file, continuing for Y lines.
The current limit is 5'000, so we could try, X=2'500 and Y=2'500.
However, most of the issue with log files is the loading time rather than the streaming time, so we could also entertain X=5'000 and Y=5'000 (which would have the same impact on load as the status quo).