Troubleshooting problems with GCS over gRPC is difficult without some telemetry indicating how the client is configured, and what load balancing information was available to the gRPC library.
When this option is enabled (the default), the GCS client will export the gRPC telemetry discussed in gRFC/66 and gRFC/78 to Google Cloud Monitoring. Google Cloud Support can use this information to more quickly diagnose problems related to GCS and gRPC.
Sending this data does not incur any billing charges, and requires minimal CPU (a single RPC every few minutes) or memory (a few KiB to batch the telemetry).
[[["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-05-07 UTC."],[[["The page provides a comprehensive list of documentation for various versions of a C++ library related to Google Cloud Storage, ranging from version 2.11.0 to the latest release candidate, 2.37.0-rc."],["The primary focus of the documentation is on `EnableGrpcMetricsOption`, which controls whether the Google Cloud Storage client exports gRPC telemetry for monitoring purposes."],["Enabling gRPC telemetry helps diagnose issues with GCS over gRPC by providing data on client configuration and load balancing, as detailed in gRPC proposals gRFC/66 and gRFC/78."],["Exporting gRPC telemetry to Google Cloud Monitoring is enabled by default and does not incur billing charges or significant CPU/memory usage."]]],[]]
