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."],[[["This webpage provides access to the documentation for `RpcMetadata` across multiple versions, from the latest release candidate `2.37.0-rc` down to version `2.10.1`."],["Each version listed, such as `2.36.0`, `2.35.0`, etc, links to the specific `RpcMetadata` documentation for that particular release."],["The `RpcMetadata` is a way to capture information about an RPC request, including headers, trailers, and socket details, once it has completed."],["The collected metadata is intended for debugging and troubleshooting purposes only, and the availability and stability of header names are not guaranteed."]]],[]]
