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 accessed through the provided link."],["The content provides a list of available versions, ranging from 2.37.0-rc down to 2.10.1, each with its own corresponding link."],["This documentation pertains to `RpcMetadata`, which includes metadata attributes made available after an RPC completes, such as headers and trailers."],["This metadata information is intended for debugging and troubleshooting, with no guarantee of header name availability or stability."]]],[]]
