Once a RPC completes the underlying transport (gRPC or HTTP) may make some metadata attributes about the request available. For the moment we just capture headers, trailers, and tunnel some low-level socket information as fake headers.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["This webpage provides a detailed version history for the `google::cloud::RpcMetadata` structure, which relates to RPC request metadata."],["The latest release candidate version is 2.37.0-rc, while the most recently released stable version is 2.36.0."],["The page contains a list of versions dating back to 2.10.1, and includes links to the documentation for each release in relation to `struct google::cloud::RpcMetadata`."],["Metadata captured by this structure, including headers, trailers, and low-level socket information, is intended for debugging and troubleshooting, with no guarantee of stability or availability of header names."]]],[]]
