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"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["This webpage provides access to the documentation for `struct google::cloud::RpcMetadata` across multiple versions."],["The latest version documented is 2.37.0-rc, with a version history going back to 2.10.1."],["The primary purpose of `RpcMetadata` is to provide information about the RPC request, including headers, trailers, and low-level socket details."],["The provided metadata is primarily intended for debugging and troubleshooting purposes, and header availability and stability are not guaranteed."]]],[]]
