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 via the provided link."],["The page provides access to documentation for a range of versions, from 2.10.1 up to the latest release candidate, 2.37.0-rc."],["This page specifically documents RPC request metadata, which becomes available after an RPC completes."],["The primary purpose of this metadata is for debugging and troubleshooting, and there's no guarantee of the availability or stability of the header names."]]],[]]
