You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add Jaeger tracing observability to OpenShift deployment
Adds Jaeger all-in-one deployment for distributed tracing support in the semantic router dashboard. Fixes the "Jaeger not configured" error on the tracing page.
Changes:
- deploy/openshift/observability/jaeger/deployment.yaml: Jaeger all-in-one container with OTLP, gRPC, HTTP, and Zipkin endpoints
- deploy/openshift/observability/jaeger/service.yaml: ClusterIP service exposing all Jaeger ports (UI:16686, OTLP:4317/4318, etc.)
- deploy/openshift/observability/jaeger/route.yaml: OpenShift route for external Jaeger UI access
Configuration:
- Memory-based trace storage (10,000 max traces)
- OTLP collector enabled for OpenTelemetry integration
- No QUERY_BASE_PATH set to allow proper static asset loading through dashboard proxy
- Security context with non-root user and dropped capabilities
- Resource limits: 512Mi-1Gi memory, 250m-500m CPU
The dashboard's existing Jaeger proxy configuration at router.go:317-350 handles proxying to http://jaeger:16686 via the TARGET_JAEGER_URL environment variable already configured in dashboard-deployment.yaml.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
Signed-off-by: Senan Zedan <[email protected]>
0 commit comments