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."],[[["The latest version available is 2.37.0-rc, which can be found with other previous versions in the list."],["This document provides access to the struct google::cloud::RpcMetadata across a variety of versions from 2.10.1 to the latest, 2.37.0-rc."],["The RpcMetadata provides metadata attributes from the underlying transport such as gRPC or HTTP once a RPC completes."],["The headers, trailers, and socket information are captured as metadata, primarily intended for debugging and troubleshooting."],["The availability and stability of header names are not guaranteed, as stated in the documentation's note."]]],[]]