Mongod is somehow sensitive to DST and putting out timestamps at +01:00, which is not technically an incorrect timestamp but it isn't useful and doesn't line up vertically.

We're clearly trying to put timestamps in GMT and failing.

This behavior seems to start at some point during server initialization, and doesn't affect all executables. mongobridge is unaffected, for example.

https://logkeeper.mongodb.org/lobster/build/ebabdaaa968aa29914a86dfffc247a2c/test/6239d498f84ae8392f66d81f#bookmarks=0%2C92%2C93%2C60413&l=1

[js_test:incremental_backup_rollback] d20030| 2022-03-22T13:52:27.485Z I  -        4672602 [-] "Testing behaviors are enabled. This has serious implications for both performance and security."
[js_test:incremental_backup_rollback] d20030| 2022-03-22T14:52:27.488+01:00 I  CONTROL  23285   [-] "Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'"

Somewhere between these lines, the mongod changed timezone.
We started out at 13:52:27.485Z, but 3 milliseconds later the logs wrote 14:52:27.488+01:00, which is in British Summer Time. That's not a timezone we should ever be using in evergreen buildhosts.