davsclaus opened a new pull request, #23817: URL: https://github.com/apache/camel/pull/23817
## Summary - When Camel profile is "dev" (default for JBang), `camel-opentelemetry2` now auto-configures an in-memory `SpanExporter` so OTel spans are captured locally without an external collector - Adds `DevSpanExporter` — bounded in-memory span storage (500 spans, LRU eviction) - Adds `OpenTelemetryDevConsole` — dev console endpoint exposing captured spans as JSON (`/q/dev/opentelemetry?dump=true`) - Production deployments (non-dev profile) are unchanged — users configure their own exporter ## How it works `OpenTelemetryTracer.initTracer()` checks the Camel context profile. If `"dev"` and no user-provided `Tracer` bean exists, it creates a local `SdkTracerProvider` with the in-memory exporter. The exporter is registered in the Camel registry so the dev console (and other tools) can query it. ## Test plan - [x] Existing `camel-opentelemetry2` tests pass (they register their own Tracer bean, so dev auto-config is correctly skipped) - [x] Build succeeds, generated service descriptors created - [ ] Manual: `camel run timer-log.yaml --observe` should log "OpenTelemetry in-memory span exporter enabled (dev profile)" - [ ] Manual: `curl http://localhost:8080/q/dev/opentelemetry?dump=true` should return captured spans 🤖 Generated with [Claude Code](https://claude.com/claude-code) on behalf of Claus Ibsen -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
