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 webpage provides documentation for `RpcMetadata` across multiple versions, ranging from version 2.10.1 to the latest release candidate, 2.37.0-rc."],["This documentation details how the underlying transport (gRPC or HTTP) captures metadata attributes such as headers, trailers, and socket information upon completion of an RPC."],["The provided metadata information, when available, is designed exclusively for debugging and troubleshooting purposes."],["The availability and stability of specific header names are not guaranteed within the `RpcMetadata` structure."]]],[]]
