flyctl logs can be out of order

I was getting some confusing debug output from flyctl logs that looks to be caused by out of order logs.

For example:

$ flyctl ssh console
# cat /etc/motd

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.

If I run that from a script set as my entrypoint, I might get something like:

2021-05-14T21:23:37.978Z app[5a5ce078] iad [info] The programs included with the Debian GNU/Linux system are free software;
2021-05-14T21:23:37.979Z app[5a5ce078] iad [info] individual files in /usr/share/doc/*/copyright.
2021-05-14T21:23:37.979Z app[5a5ce078] iad [info] the exact distribution terms for each program are described in the
2021-05-14T21:23:37.980Z app[5a5ce078] iad [info] permitted by applicable law.
2021-05-14T21:23:37.980Z app[5a5ce078] iad [info] Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent

It looks like log lines with the same timestamp are the culprit.

We’re looking at this. They should be nanosecond precision, but there’s a chance we’re truncating timestamps somewhere in the chain.

@simon-weber This should now be fixed. We were truncating to milliseconds at 2 places in our logs pipeline.

Thanks!