Environment Variables

A number of environment variables can be used to configure the behavior of the library. There are also functions to configure this behavior in code. The environment variables are convenient when troubleshooting problems.

Endpoint Overrides

BIGTABLE_EMULATOR_HOST=host:port: tells the library to connect to the specified emulator rather than the default endpoint. Intended for testing only.

See Also

google::cloud::EndpointOption

Logging

GOOGLE_CLOUD_CPP_ENABLE_TRACING=rpc: turns on tracing for most gRPC calls. The library injects an additional Stub decorator that prints each gRPC request and response. Unless you have configured your own logging backend, you should also set GOOGLE_CLOUD_CPP_ENABLE_CLOG to produce any output on the program's console.

GOOGLE_CLOUD_CPP_ENABLE_TRACING=rpc-streams: turns on tracing for streaming gRPC calls, such as Table::ReadRows(). Be warned that streams produce a lot of output.

GOOGLE_CLOUD_CPP_ENABLE_TRACING=rpc,rpc-streams: turns on tracing for both regular RPC calls and streaming RPC calls.

See Also

google::cloud::LoggingComponentsOptionGOOGLE_CLOUD_CPP_TRACING_OPTIONS=...: modifies the behavior of gRPC tracing, including whether messages will be output on multiple lines, or whether string/bytes fields will be truncated.

See Also

google::cloud::GrpcTracingOptionsOptionGOOGLE_CLOUD_CPP_ENABLE_CLOG=yes: turns on logging in the library, basically the library always "logs" but the logging infrastructure has no backend to actually print anything until the application sets a backend or they set this environment variable.

See Also

google::cloud::LogBackend

See Also

google::cloud::LogSink

Setting the Default Project

GOOGLE_CLOUD_PROJECT=...: is used in examples and integration tests to configure the GCP project. This has no effect in the library.