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 is a release candidate."],["This page provides access to documentation for multiple versions of RPC metadata, from version 2.10.1 up to the latest release candidate."],["The content on this page covers RPC request metadata, specifically focusing on headers, trailers, and socket information that are available upon RPC completion."],["The captured metadata information is designed for debugging and troubleshooting, with no guarantee of header name availability or stability."]]],[]]
