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 accessed via a link."],["This webpage provides documentation for the `RpcMetadata` struct within the Google Cloud C++ client library across multiple versions."],["The `RpcMetadata` struct stores data about a completed RPC request, which can be used for debugging and troubleshooting."],["There are many previous versions listed, with version 2.27.0 indicating the starting point of the information in the content, and 2.10.1 showing as the oldest."],["The metadata is primarily for debugging and may not be stable or available in all cases, as the information is intended for troubleshooting purposes only, with no guarantees about availability or stability of header names."]]],[]]
