Add Google Cloud OpenTelemetry plugin#2954
Closed
eamsden wants to merge 1 commit into
Closed
Conversation
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
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.
What was changed
temporal-gcpmodule andGcpOpenTelemetryPluginas a thin Google Cloud Run configuration layer overtemporal-opentelemetry.Why?
Temporal Java workers running on Google Cloud Run need an SDK-supported path for exporting Temporal metrics and traces through the standard local OTLP collector sidecar. Keeping Google resource detection and exporters in the collector avoids Google Cloud client dependencies and direct-export configuration in the worker process.
Checklist
Closes: N/A.
How was this tested:
./gradlew :temporal-gcp:build :temporal-bom:generatePomFileForMavenJavaPublication --offlinetemporal-gcpPOM only publishestemporal-opentelemetryas a dependency.Any docs updates needed?
contrib/temporal-gcp/README.mdwith setup, precedence, lifecycle, and collector-sidecar requirements.Breaking changes?
No.
Server PR
None.