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-04-09 UTC."],[[["The webpage provides documentation for `RpcMetadata` within the Google Cloud C++ client library."],["Version 2.37.0-rc is the latest available version, but there are many other documented releases ranging back to version 2.10.1."],["The `RpcMetadata` captures information such as request headers and trailers, along with some low-level socket details, once an RPC has completed."],["The `RpcMetadata` is intended for debugging and troubleshooting purposes only, and header names are not guaranteed to be stable or consistently available."]]],[]]
