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 `structgoogle::cloud::RpcMetadata` across multiple versions, from 2.10.1 up to the latest release candidate 2.37.0-rc."],["The primary focus of the documentation is on RPC request metadata, which becomes available after an RPC operation completes, regardless of if it uses gRPC or HTTP."],["The available metadata includes headers, trailers, and low-level socket details presented as headers."],["The metadata provided is intended for debugging and troubleshooting, with no guarantees of stability or availability of header names."]]],[]]
