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 versioned documentation in the provided list."],["This page documents the `RpcMetadata` struct, a part of the Google Cloud C++ client library, across multiple versions."],["The `RpcMetadata` struct contains metadata attributes about a completed RPC request, such as headers, trailers, and socket information."],["The information within `RpcMetadata` is intended for debugging and troubleshooting purposes, and the availability or stability of header names is not guaranteed."],["The documented versions include all versions from 2.10.1 to 2.37.0-rc, each with a dedicated link."]]],[]]
