Release Highlights

• Platform Operators can now experience easier debugging using human-readable timestamps based on configuration in gorouter.stdout.log details

• We received feedback that the access.log app_time metric is ambiguous since it includes network time and not just application time. To avoid any confusion for application developers, the gorouter access.log no longer emits the app_time metric details

• Breaking change: Requests with nonexistent instance ID headers and with syntactically incorrect instance ID headers will now return a 400 status code instead of a 404 status code. A 400 status code indicates that the server cannot or will not process the request due to a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).