Log date time stamp format changed in 1.5.0-rc.1 - please revert

[begunfx]

This is what I see now in the log. It was more readable in 1.4.5. Can we please revert it? Thanks!

2026-03-24T15:56:13.362Z
info
registry.mau.public
Register with configuration {}
5
2026-03-24T15:56:13.363Z
info
registry.alicr.public
Register with configuration {}
6
2026-03-24T15:56:13.364Z
info
registry.ibmcr.public
Register with configuration {}
7
2026-03-24T15:56:13.365Z
info
registry.lscr.public
Register with configuration {}
8
2026-03-24T15:56:13.366Z
info
registry.ocir.public
Register with configuration {}
9
2026-03-24T15:56:13.367Z
info
registry.quay.public
Register with configuration {}
10
2026-03-24T15:56:13.368Z
info
registry.docr.public
Register with configuration {}

[s-b-e-n-s-o-n]

Fixed in rc.2. The root cause was the pino-pretty log formatter — when we moved it from a shell pipe to an in-app stream in v1.5.0-rc.1, pino-pretty's default behavior is to print extra fields (like component and container) on indented lines below the main log entry. This made docker logs output look fragmented compared to v1.4.5.

The fix enables singleLine mode in pino-pretty, so all fields now stay on one line:

Before (rc.1):

[15:56:13.362] INFO (drydock/7): Register with configuration {}
    component: "registry.mau.public"

After (rc.2):

[15:56:13.362] INFO (drydock/7): Register with configuration {} {"component":"registry.mau.public"}

Everything on a single line, much easier to scan in docker logs output.

[begunfx]

My call out here was not the line wrapping (although I agree that should be fixed) but the timestamp format had changed. It was in a easily digestable time format but now is hard to decipher 2026-03-24T15:56:13.362Z

[s-b-e-n-s-o-n]

You were right to call this out separately from the line-wrapping issue.

singleLine fixed the extra fields being split across multiple lines, but the timestamp complaint was a different regression: the release image had started defaulting to DD_LOG_FORMAT=json, so docker logs was showing raw JSON timestamps like 2026-03-24T15:56:13.362Z instead of the old pretty text output.

That is now fixed in rc.2 as well. The official image default has been switched back to DD_LOG_FORMAT=text, which restores the human-readable docker logs format from v1.4.5, including the short pretty timestamp. JSON output is still available explicitly with DD_LOG_FORMAT=json if someone wants structured logs.

[s-b-e-n-s-o-n]

Fixed in v1.5.0-rc.2. The release Docker image now defaults back to DD_LOG_FORMAT=text, restoring human-readable docker logs output. Set DD_LOG_FORMAT=json explicitly if you want structured log output.

[begunfx]

Still not seeing a more friendly timestamp.

See screenshot:

[s-b-e-n-s-o-n]

Good catch — the rc.2 fix restored text mode but did not change the timestamp format. pino-pretty was still using its default ISO timestamp (2026-03-24T15:56:13.362Z) instead of a human-readable local time.

For rc.3 we've explicitly set translateTime: 'SYS:HH:MM:ss.l' in the pretty formatter, so docker logs will now show timestamps like:

[11:56:13.362] INFO (drydock): Register with configuration {}

Also added regression tests to pin this format so it can't silently revert again. Please verify once rc.3 is out.

[s-b-e-n-s-o-n]

Fixed in v1.5.0-rc.3. Timestamps now use human-readable local time format. Please update and let us know if this resolves the issue.

[begunfx]

Unfortunately, still an issue with rc.3:

[s-b-e-n-s-o-n]

Thanks for the screenshot — that confirms the remaining issue is in the in-app system log viewer (Settings > System Logs), not docker logs output.

rc.3 fixed the docker logs timestamps (pino-pretty translateTime), but the UI log viewer had its own separate timestamp formatter that was still using ISO format (toISOString()). There were actually four independent timestamp surfaces that had drifted apart:

1. Backend stdout (docker logs) — fixed in rc.3
2. System log REST API → UI log viewer — was still ISO
3. System log WebSocket stream → UI log viewer — was still ISO
4. Container log WebSocket stream — had yet another format

We've now unified all of them behind a single shared display-timestamp module. Every log surface (backend stdout, system log viewer, container log viewer, agent-proxied logs) now produces the same [HH:MM:ss.sss] format. This will ship in the next RC.

[s-b-e-n-s-o-n]

Fixed in v1.5.0-rc.4. Unified display-timestamp module now covers all log surfaces including the system log viewer. Please update and let us know if this resolves the issue.

[begunfx]

Timestamp is now human readable as expected in the drydock logs. Thank you.

Feel free to close this. Thanks!