Deprecate the exporters and related artifacts#441
Draft
psx95 wants to merge 10 commits into
Draft
Conversation
psx95
force-pushed
the
release-minor-version
branch
from
6d7912b to
6507068
Compare
psx95
changed the title
dashpole
reviewed
May 8, 2026
psx95
force-pushed
the
release-minor-version
branch
from
50e8f0d to
ab54b0d
Compare
dashpole
reviewed
May 18, 2026
dashpole
reviewed
May 18, 2026
dashpole
reviewed
May 18, 2026
| | `setCredentials(Credentials)` | Pass the bearer token as Authorization Header in the exporter | Handled automatically by `opentelemetry-gcp-auth-extension`. | | ||
| | `setMetricServiceEndpoint(String)` | `otel.exporter.otlp.endpoint` / `OTEL_EXPORTER_OTLP_ENDPOINT` | Set it to `https://telemetry.googleapis.com` to send metrics to Google Cloud. | | ||
| | `setDeadline(Duration)` | `otel.exporter.otlp.timeout` / `OTEL_EXPORTER_OTLP_TIMEOUT` | Default is 10 seconds. | | ||
| | `setPrefix(String)` | N/A | The Telemetry API automatically prefixes metrics with `prometheus.googleapis.com/` by default and will be stored in Google Managed Prometheus with `prometheus_target` as the Monitored Resource. Custom prefixes are not directly supported via OTLP exporter configuration.<br>If you want your metric to keep appearing under your previous prefix (e.g., `workload.googleapis.com`), you must include the full prefix in the metric name you define in your OpenTelemetry instrumentation. | |
Contributor
There was a problem hiding this comment.
I don't think this is going to be acceptable. We need to find a way for users to migrate to the OTLP exporter without breaking dashboards. There must be some way to do that, right? Is it possible with a view in java? Or do we need to show users how to "wrap" their OTLP exporter to update metric names during the migration?
aabmass
reviewed
May 18, 2026
Contributor
There was a problem hiding this comment.
This seems duplicative of https://docs.cloud.google.com/trace/docs/migrate-to-otlp-endpoints
do we need both ?
Contributor
Author
There was a problem hiding this comment.
The trace one is, but this document has a little more information. Eventually we plan to update https://docs.cloud.google.com/trace/docs/migrate-to-otlp-endpoints and have that as single source of truth.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR marks the public APIs of the artifacts released from this repository as deprecated and also emits deprecation warnings during runtime in form of logs in case any of these artifacts are used in an application.
The PR also adds a migration guide, which will hold instructions for users to follow while moving from the OpenTelemetry Google Cloud Monitoring and Trace exporters to OpenTelemetry OTLP exporters.