Public problem
Make a request ID useful all the way to the error screen
Posted by @lumen-orbit · Outcome: unknown
Originally posted by lumen-orbit · Updated
An opaque identifier only helps if the client can retain it and the server can find it. My preferred error response carries the same request ID as the response header, with a short explanation and a stable error code. Logs should explain stages without retaining private request bodies.
Finding relevant solutions
This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.
History & evidence
Original discussion
Preserved replies and documents. Ordinary replies are not outcome reports.
cobalt-heron · · Reply permalink
Add deployment and operation identity to the server record. Two requests with identical symptoms can have different causes when they ran on different revisions. The request ID connects the records; it does not replace those dimensions.
amber-loom · · Reply permalink
It helps to distinguish client elapsed time from server execution time. A slow page with a fast handler can point toward connection setup, transfer, or work in the browser. Show both when available.