Claude/serene albattani 0 yt hg - #473
Merged
Merged
Conversation
The Jaeger native exporters were removed from the OpenTelemetry SDK (>=1.28). In production the OTel operator injects a recent SDK at /otel-auto-instrumentation-python and prepends it to PYTHONPATH, so the pinned opentelemetry-exporter-jaeger==1.21.0 crashed on startup with: ImportError: cannot import name 'OTEL_EXPORTER_JAEGER_AGENT_HOST' from 'opentelemetry.sdk.environment_variables' Switch to the OTLP gRPC span exporter (Jaeger ingests OTLP natively on 4317). With no configured endpoint the exporter reads the standard OTEL_EXPORTER_OTLP_ENDPOINT env var that the operator injects, so prod defers to the operator while local dev points at the jaeger service. - server.py: JaegerExporter -> OTLPSpanExporter - config.py: replace jaeger_host/jaeger_port with otlp_endpoint - requirements: drop opentelemetry-exporter-jaeger, add otlp-proto-grpc - docker-compose.dev.yml: expose Jaeger OTLP ports, set OTLP_ENDPOINT https://claude.ai/code/session_01MjikEyt2y77SdaTHJ1oLoo
Keep the existing JAEGER_HOST/JAEGER_PORT configuration instead of
introducing a new OTLP_ENDPOINT variable. The OTLP exporter endpoint is
constructed as http://{jaeger_host}:{jaeger_port}; the default port moves
from 6831 (old thrift agent) to 4317 (Jaeger's native OTLP gRPC receiver).
https://claude.ai/code/session_01MjikEyt2y77SdaTHJ1oLoo
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
2 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.
The Jaeger native exporters were removed from the OpenTelemetry SDK (>=1.28). In production the OTel operator injects a recent SDK at /otel-auto-instrumentation-python and prepends it to PYTHONPATH, so the pinned opentelemetry-exporter-jaeger==1.21.0 crashed on startup with:
ImportError: cannot import name 'OTEL_EXPORTER_JAEGER_AGENT_HOST'
from 'opentelemetry.sdk.environment_variables'
Switch to the OTLP gRPC span exporter (Jaeger ingests OTLP natively on 4317). With no configured endpoint the exporter reads the standard OTEL_EXPORTER_OTLP_ENDPOINT env var that the operator injects, so prod defers to the operator while local dev points at the jaeger service.