[
https://issues.apache.org/jira/browse/CAMEL-23706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-23706:
--------------------------------
Component/s: camel-opentelemetry
> camel-opentelemetry2 - Auto-configure in-memory span exporter for dev profile
> -----------------------------------------------------------------------------
>
> Key: CAMEL-23706
> URL: https://issues.apache.org/jira/browse/CAMEL-23706
> Project: Camel
> Issue Type: Improvement
> Components: camel-opentelemetry
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 4.21.0
>
>
> When the Camel profile is "dev" (default for JBang), camel-opentelemetry2
> should auto-configure an in-memory SpanExporter so that OTel spans are
> captured locally without requiring an external collector.
> Currently, camel run --observe adds camel-opentelemetry2 which has the OTel
> SDK on the classpath, but no SpanExporter is configured.
> GlobalOpenTelemetry.get() returns a no-op instance, so all OTel spans are
> silently dropped.
> This adds:
> - DevSpanExporter: a bounded in-memory SpanExporter (500 spans, LRU eviction)
> - OpenTelemetryDevConsole: a dev console endpoint exposing captured spans as
> JSON
> - Profile detection in OpenTelemetryTracer.initTracer(): when profile is
> "dev" and no user-provided Tracer exists, auto-configure SdkTracerProvider
> with the in-memory exporter
> For production deployments (non-dev profile), behavior is unchanged.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
