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
Right now it's only possible to read job's logs from the end with --tail flag. This makes it hardly possible to look up the logs from a few days ago (--tail=1000000 in combination of a lot of patience). There should be --since parameter (and maybe --until) allowing to do that like it is in docker:
--since="" Show logs since timestamp (e.g. 2013-01-02T13:23:37Z) or rela‐
tive (e.g. 42m for 42 minutes)
-n, --tail="all" Number of lines to show from the end of the logs
--until="" Show logs before a timestamp (e.g. 2013-01-02T13:23:37Z) or rel‐
ative (e.g. 42m for 42 minutes)
It refers to reading logs by CLI Racetrack client, but maybe this mechanism could be implemented in Dashboard ("Runtime logs" button) too, if possible.
The text was updated successfully, but these errors were encountered:
No one asked about it now. Maybe some day someone complained about too much logs to browse, but it was 11 months ago when the original issue was created. I've transferred it from an old issue tracker.
Right now it's only possible to read job's logs from the end with
--tail
flag. This makes it hardly possible to look up the logs from a few days ago (--tail=1000000
in combination of a lot of patience). There should be--since
parameter (and maybe--until
) allowing to do that like it is in docker:It refers to reading logs by CLI Racetrack client, but maybe this mechanism could be implemented in Dashboard ("Runtime logs" button) too, if possible.
The text was updated successfully, but these errors were encountered: