-
Notifications
You must be signed in to change notification settings - Fork 39
Deprecate the exporters and related artifacts #441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,22 @@ | ||
| # Migration Guide | ||
|
|
||
| This guide provides instructions on how to migrate from the custom exporters in this repository to the standard OpenTelemetry OTLP exporters. | ||
|
|
||
| ## Overview | ||
| Google Cloud now supports native OTLP (OpenTelemetry Protocol) ingestion for Cloud Trace and Cloud Monitoring via the [Telemetry API](https://docs.cloud.google.com/stackdriver/docs/reference/telemetry/overview). This allows you to use the standard OpenTelemetry OTLP exporters for sending telemetry data to Google Cloud. | ||
|
|
||
| ## Migrate from OpenTelemetry Google Cloud Trace Exporter to OTLP exporter | ||
|
|
||
| Follow the [Migrate from the Trace exporter to the OTLP endpoint](https://docs.cloud.google.com/trace/docs/migrate-to-otlp-endpoints) guide for migration instructions. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think you can use https://docs.cloud.google.com/trace/docs/migrate-to-otlp-endpoints#java_3 to make sure it shows the java samples? |
||
|
|
||
| ## Migrate from OpenTelemetry Google Cloud Monitoring Exporter to OTLP exporter | ||
|
|
||
| > [!NOTE] The Google Cloud OTLP metrics endpoint is currently in preview and the migration guides are being developed. | ||
|
|
||
| TODO: Add migration guide for metrics exporter | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Things to cover for metrics other than just the default "make it work":
|
||
|
|
||
| ## Migrate from OpenTelemetry Google Cloud Auto Exporter | ||
|
|
||
| The Auto exporter allowed the [auto-configuration module](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure#opentelemetry-sdk-autoconfigure) of OpenTelemetry Java to work with OpenTelemetry Google Cloud Trace and Monitoring exporters in this repository. | ||
|
|
||
| The standard OpenTelemetry OTLP exporters natively support auto-configuration and are the recommended way to send telemetry to Google Cloud. You can configure the OTLP exporters using the standard [exporter properties](https://opentelemetry.io/docs/languages/java/configuration/#properties-exporters) that are supported by the autoconfiguration module. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was imagining this would be fairly detailed, but I guess it doesn't have to be if it is covered in the GCP docs. We should make sure we tell users of each of the configuration options how they can obtain the same behavior with the OTLP exporter: