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 documents different versions of `google::cloud::RpcMetadata`, starting from version 2.10.1 up to the latest release candidate, version 2.37.0-rc."],["The primary function of `RpcMetadata` is to capture metadata attributes made available by the underlying transport layer (gRPC or HTTP) once an RPC completes."],["The metadata captured by `RpcMetadata` includes headers, trailers, and low-level socket information, although this information is intended for debugging and troubleshooting purposes."],["The version that the page is on is 2.21.0, which is not the latest."]]],[]]
