Client libraries

Note: Trace data is automatically captured for some configurations, so you might not need to instrument your application. For more information, see Configurations with automatic tracing.

When trace data isn't automatically captured, you need to instrument your application to collect this data.

You can instrument your application so that it collects application-specific information. Several open-source instrumentation frameworks let you collect metrics, logs, and traces from your application and send that data to any vendor, including Google Cloud. To instrument your application, we recommend that you use a vendor-neutral instrumentation framework that is open source, such as OpenTelemetry, instead of vendor- and product-specific APIs or client libraries.

For information about instrumenting your applications by using vendor-neutral instrumentation frameworks, see Instrumentation and observability.

Set up information for the OpenTelemetry library:

• C++
• Go
• Java
• Node.js
• Python

Information about the Cloud Client Libraries:

• Ruby:

  Note: We recommend that you use OpenTelemetry for Ruby. For more information, see the Ruby SDK.

  GitHub: googleapis/google-cloud-trace

• ASP.NET:

  • Library: Google.Cloud.Diagnostics.AspNet
  • NuGet package: Google.Cloud.Diagnostics.AspNet
  • GitHub: Google.Cloud.Diagnostics.AspNet version 4.0.0

• ASP.NET Core:

  • Libraries: Google.Cloud.Diagnostics.AspNetCore3 and Google.Cloud.Diagnostics.AspNetCore
  • NuGet packages: Google.Cloud.Diagnostics.AspNetCore3 and Google.Cloud.Diagnostics.AspNetCore
  • GitHub: googleapis/google-cloud-dotnet

You can also receive traces from Zipkin tracers. For more information, go to Using Cloud Trace with Zipkin.