is defining the GOOGLE_CLOUD_CPP_OPENTELEMETRY_TRACING environment variable all I need?

[willie]

I have a C++ program that I recently added OpenTelemetry instrumentation to. Same program uses Cloud Storage, as well. In vcpkg (very recent version), I added the opentelemetry feature to google-cloud-cpp in my manifest, and I've defined GOOGLE_CLOUD_CPP_OPENTELEMETRY_TRACING as an environmental variable.

I've not changed any other code, as I've already defined a global exporter, etc. in my existing code. I'm not sending my Otel data to Cloud Trace, FWIW, but I'm seeing all of my traces, etc. in Uptrace where I have things configured, so I'm pretty sure that isn't the problem.

Is there more I have to do to make this work?

[dbolduc]

Argh, sorry, this is a bug. Thanks for the report.

In the latest version of google-cloud-cpp, the storage and bigtable libraries do not respect the GOOGLE_CLOUD_CPP_OPENTELEMETRY_TRACING variable. This is not by design. It was an oversight.

I fixed this for bigtable in #13748. I will send a PR to fix storage.

I think your options are to:

A. Explicitly set OpenTelemetryTracingOption in your client. e.g.

google-cloud-cpp/google/cloud/opentelemetry/quickstart/quickstart.cc

Lines 38 to 40 in 8ca67ec

	// Create a client with OpenTelemetry tracing enabled.
	auto options = gc::Options{}.set<gc::OpenTelemetryTracingOption>(true);
	auto client = gcs::Client(options);

B. Wait for us to make the fix, release a new version of google-cloud-cpp, and push that version to vcpkg. This will not get completed until April.

Sorry for the trouble.

[willie]

I appreciate the reply and workaround! Option A immediately solved my problem. Thank you!

[dbolduc]

Cool. I am glad your problem is solved!

FWIW, I sent #13766 to fix the handling in the storage::Client.