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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-26 UTC."],[[["This webpage documents different versions of `RpcMetadata`, with the latest release candidate being version 2.37.0-rc."],["The page provides links to documentation for various versions of `RpcMetadata` ranging from 2.10.1 up to the latest 2.37.0-rc version, including each minor and patch update."],["`RpcMetadata` captures metadata attributes such as headers and trailers, potentially exposing low-level socket information for debugging."],["The metadata available through `RpcMetadata` is intended strictly for debugging and troubleshooting, with no guarantees of stability or availability of specific header names."]]],[]]
