davsclaus opened a new pull request, #23868: URL: https://github.com/apache/camel/pull/23868
## Summary - Add `--open-telemetry-agent` flag to `camel run/dev/debug` that attaches the OpenTelemetry Java Agent and configures an embedded OTLP receiver inside the Camel process - The agent's protobuf-encoded spans are received on `/v1/traces` and fed into the in-memory `DevSpanExporter` — zero config, no external collector needed - Spans are visible in the TUI OTel Spans tab and through the dev console - Add Process tab in TUI (under More popup) showing PID, Java version, command line, and process metadata - Add F2 OTel Agent checkbox in the run options form - Manage `opentelemetry-proto` version in parent POM with `provided` scope ## How it works 1. `--open-telemetry-agent` triggers JBang subprocess re-launch with the OTel Java Agent attached 2. The agent is configured to export traces to `http://localhost:<port>/v1/traces` (the embedded receiver) 3. `OpenTelemetryTracer.initOtlpReceiver()` creates a `platform-http` route that receives OTLP protobuf payloads 4. `OtlpReceiverProcessor` parses the protobuf into `SpanData` and feeds them to `DevSpanExporter` 5. The TUI reads from `DevSpanExporter` and displays spans in the OTel Spans tab ## Test plan - [x] `camel run --open-telemetry-agent --example=timer-log` — agent attaches, receiver starts, spans flow without warnings - [x] Spans visible in TUI OTel Spans tab - [x] No protobuf dependency pulled transitively for regular `camel-opentelemetry2` users (provided scope) - [ ] CI build passes _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]
