shashankbhatgs opened a new pull request, #14010:
URL: https://github.com/apache/trafficserver/pull/14010

   `diags.log` and `traffic.out` stamp lines like `[Oct  8 18:58:01.123]`, with 
no year and no time zone. `error.log` uses `20261008.18h58m01s`, to the whole 
second. Both are in local time, so lines can't be matched across these logs or 
across hosts without parsing two formats and guessing the year and zone.
   
   This is step 1 of #12944: all three logs now use ISO 8601 in UTC with 
milliseconds, for example `2026-10-08T18:58:01.123Z`.
   
   - `ts::format_iso8601_utc` in `tsutil` writes the stamp, and both the diags 
formatter (`DbgCtl.cc`) and `LogObject::va_log` call it, so the formats can't 
drift apart.
   - `LogUtils::timestamp_to_str` had no other callers and is removed. Rolled 
log file names come from `BaseLogFile` and are unchanged.
   - `upgrading.en.rst` notes the change for anyone parsing these logs.
   
   One effect to flag: plugin text logs created with 
`TSTextLogObjectCreate(..., TS_LOG_MODE_ADD_TIMESTAMP, ...)` share the 
`error.log` code path, so they change too. I kept them consistent with 
`error.log` and called it out in the release note. Happy to limit the change to 
`error.log` if you'd rather.
   
   Testing: new Catch2 test `test_ts_iso8601.cc`, and the full ctest suite 
passes locally (macOS). I also ran `traffic_server` locally with a remap to a 
closed port and checked that one failed connection shows the same stamp in 
`error.log` and `traffic.out`:
   
   ```
   2026-11-06T15:29:02.138Z CONNECT: attempt fail [CONNECTION_ERROR] to 
127.0.0.1:9 ... sm_id=2 ...
   [2026-11-06T15:29:02.138Z] [ET_NET 10] DIAG: ... (http_seq) [2] Entering 
HttpTransact::handle_server_connection_not_open
   ```
   
   Part of #12944
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to