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 a specific link."],["The current version of this documentation is 2.36.0, but it includes access to documentation of many previous versions, ranging down to 2.10.1."],["The documentation concerns `RpcMetadata`, which captures information about an RPC's headers, trailers, and socket data after it completes."],["The information provided is solely intended for debugging and troubleshooting purposes and it is not guaranteed that header names will always be available."]]],[]]
