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 2.10.1 to the latest release candidate, 2.37.0-rc."],["The latest available version for `RpcMetadata` is 2.37.0-rc, and 2.34.0 is the version currently displayed."],["`RpcMetadata` captures request metadata like headers and trailers from underlying transports, such as gRPC or HTTP."],["The metadata provided through `RpcMetadata` is primarily for debugging and troubleshooting, and the availability and stability of header names are not guaranteed."]]],[]]
