This is an automated email from the ASF dual-hosted git repository. pcongiusti pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit 691a5152d10ed6508ce83b6c8720905d99f08ac9 Author: Pranjul Kalsi <[email protected]> AuthorDate: Fri Dec 12 15:31:28 2025 +0530 add migration guide for deprecated telemetry trait --- docs/modules/traits/pages/telemetry.adoc | 72 ++++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) diff --git a/docs/modules/traits/pages/telemetry.adoc b/docs/modules/traits/pages/telemetry.adoc index 70abecc87..801602cea 100644 --- a/docs/modules/traits/pages/telemetry.adoc +++ b/docs/modules/traits/pages/telemetry.adoc @@ -4,6 +4,14 @@ [.badges] [.badge-key]##Deprecated since##[.badge-unsupported]##2.9.0## // End of autogenerated code - DO NOT EDIT! (badges) + +[WARNING] +==== +The Telemetry trait is *deprecated* as of version 2.9.0 and will be removed in a future release. + +The same behavior can be achieved via properties and dependencies configuration. See the <<migration-guide>> section below for details. +==== + // Start of autogenerated code - DO NOT EDIT! (description) The Telemetry trait can be used to automatically publish tracing information to an OTLP compatible collector. @@ -92,3 +100,67 @@ $ kamel run -t telemetry.enable=true -t telemetry.service-name=tracer_myintegrat + [source,console] $ kamel run -t telemetry.enable=true -t telemetry.sampler=ratio -t telemetry.sampler-ratio=0.001 ... + +[[migration-guide]] +== Migration Guide + +The Telemetry trait is deprecated. The same behavior can be achieved via properties and dependencies configuration. + +=== Property Mapping + +The following table shows how to map Telemetry trait properties to application properties: + +[cols="2m,2m,3a"] +|=== +|Telemetry Trait | Application Property | Example + +| telemetry.endpoint=http://jaeger:4317 +| quarkus.otel.exporter.otlp.traces.endpoint=http://jaeger:4317 +| `kamel run -p quarkus.otel.exporter.otlp.traces.endpoint=http://jaeger:4317 MyRoute.java` + +| telemetry.service-name=my-service +| quarkus.otel.resource.attributes=service.name=my-service +| `kamel run -p quarkus.otel.resource.attributes=service.name=my-service MyRoute.java` + +| telemetry.sampler=ratio +| quarkus.otel.traces.sampler=ratio +| `kamel run -p quarkus.otel.traces.sampler=ratio MyRoute.java` + +| telemetry.sampler-ratio=0.001 +| quarkus.otel.traces.sampler.ratio=0.001 +| `kamel run -p quarkus.otel.traces.sampler.ratio=0.001 MyRoute.java` + +| telemetry.sampler-parent-based=true +| quarkus.otel.traces.sampler.parent-based=true +| `kamel run -p quarkus.otel.traces.sampler.parent-based=true MyRoute.java` + +|=== + +=== Migration Examples + +**Before (deprecated):** + +[source,console] +---- +$ kamel run -t telemetry.enabled=true \ + -t telemetry.endpoint=http://jaeger:4317 \ + -t telemetry.service-name=my-integration \ + MyRoute.java +---- + +**After (recommended):** + +[source,console] +---- +$ kamel run \ + -p quarkus.otel.exporter.otlp.traces.endpoint=http://jaeger:4317 \ + -p quarkus.otel.resource.attributes=service.name=my-integration \ + MyRoute.java +---- + +=== Benefits of Direct Configuration + +Using properties and dependencies configuration directly provides more flexibility, including: + +* Full access to all Quarkus OpenTelemetry options: https://quarkus.io/guides/opentelemetry +* Custom telemetry dependencies can be added as needed
