Troubleshoot Cloud Client Libraries for Rust

This document explains how to troubleshoot issues with the Cloud Client Libraries for Rust, including enabling debug logs, tracing gRPC transport calls, diagnosing proxy issues, and reporting problems.

Debug logging

To diagnose request and response issues, enable client library logging. For more information, see Enable logging.

Trace gRPC issues

Clients that use gRPC rely on tonic for the underlying transport. To debug gRPC calls in Rust, use tracing subscriber filters to inspect specific gRPC and HTTP/2 crates.

For example, set the RUST_LOG environment variable to include tonic=debug or h2=debug to inspect gRPC and HTTP/2 transport details:

RUST_LOG=tonic=debug,h2=debug cargo run --example EXAMPLE_NAME

Replace <var>EXAMPLE_NAME</var> with the name of your Cargo example.

Diagnose proxy issues

For information about configuring HTTP proxies, see Configure a proxy.

Report a problem

If you still can't resolve your issue, get help using one of the following options:

  • With a Google Cloud support contract: Create a case through Google Cloud Support instead of filing an issue on GitHub. Creating a support case ensures a timely response.
  • Without a support contract: File an issue in the google-cloud-rust repository on GitHub. Although Google Cloud client libraries use multiple GitHub repositories, file Rust issues in google-cloud-rust unless you're certain the issue belongs elsewhere. The maintainers might move the issue to a different repository if needed, and GitHub notifies the email address associated with your GitHub account.