Provide equivalent of OTel's Jaeger exporter for Helidon compatibility (helidon-io#11112)

Author: tjquinno

all/pom.xml

@@ -620,6 +620,10 @@
             <groupId>io.helidon.tracing.providers</groupId>
             <artifactId>helidon-tracing-providers-jaeger</artifactId>
         </dependency>
+        <dependency>
+            <groupId>io.helidon.tracing</groupId>
+            <artifactId>helidon-tracing-exporter-jaeger</artifactId>
+        </dependency>
         <dependency>
             <groupId>io.helidon.tracing</groupId>
             <artifactId>helidon-tracing-tracer-resolver</artifactId>

bom/pom.xml

@@ -845,6 +845,11 @@
                 <artifactId>helidon-tracing-providers-jaeger</artifactId>
                 <version>${helidon.version}</version>
             </dependency>
+            <dependency>
+                <groupId>io.helidon.tracing</groupId>
+                <artifactId>helidon-tracing-exporter-jaeger</artifactId>
+                <version>${helidon.version}</version>
+            </dependency>
             <dependency>
                 <!-- to add TracerResolver support -->
                 <groupId>io.helidon.tracing</groupId>

dependencies/pom.xml

@@ -62,6 +62,7 @@
         <version.lib.graphql-java.extended.scalars>22.0</version.lib.graphql-java.extended.scalars>
         <version.lib.gson>2.13.2</version.lib.gson>
         <version.lib.grpc>1.73.0</version.lib.grpc>
+        <version.lib.google-findbugs-jsr305>3.0.2</version.lib.google-findbugs-jsr305>
         <version.lib.guava>33.3.1-jre</version.lib.guava>
         <version.lib.h2>2.4.240</version.lib.h2>
         <version.lib.hamcrest>1.3</version.lib.hamcrest>
@@ -254,6 +255,22 @@
                 <artifactId>opentelemetry-semconv</artifactId>
                 <version>${version.lib.opentelemetry.semconv}</version>
             </dependency>
+            <!--
+            By default, OpenTelemetry's OTLP exporter uses okhttp. To reduce 3rd-party dependencies and more easily
+            manage dependency convergence use the OpenTelemetry JDK client support instead.
+            -->
+            <dependency>
+                <groupId>io.opentelemetry</groupId>
+                <artifactId>opentelemetry-exporter-otlp</artifactId>
+                <version>${version.lib.opentelemetry}</version>
+                <exclusions>
+                    <exclusion>
+                        <groupId>io.opentelemetry</groupId>
+                        <artifactId>opentelemetry-exporter-sender-okhttp</artifactId>
+                    </exclusion>
+                </exclusions>
+            </dependency>
+            <!-- -->
             <dependency>
                 <groupId>io.opentracing</groupId>
                 <artifactId>opentracing-util</artifactId>
@@ -369,11 +386,11 @@
                 <artifactId>jakarta.interceptor-api</artifactId>
                 <version>${version.lib.jakarta.interceptor-api}</version>
                 <exclusions>
-                  <!-- Exclude EJB. See https://github.com/eclipse-ee4j/interceptor-api/issues/31 -->
-                  <exclusion>
-                      <groupId>jakarta.ejb</groupId>
-                      <artifactId>jakarta.ejb-api</artifactId>
-                  </exclusion>
+                    <!-- Exclude EJB. See https://github.com/eclipse-ee4j/interceptor-api/issues/31 -->
+                    <exclusion>
+                        <groupId>jakarta.ejb</groupId>
+                        <artifactId>jakarta.ejb-api</artifactId>
+                    </exclusion>
                 </exclusions>
             </dependency>
             <dependency>
@@ -1231,10 +1248,9 @@
                 <version>${version.lib.okio}</version>
             </dependency>
             <dependency>
-                <!-- For dependency convergence -->
-                <groupId>com.squareup.okio</groupId>
-                <artifactId>okio-jvm</artifactId>
-                <version>${version.lib.okio}</version>
+                <groupId>com.google.code.findbugs</groupId>
+                <artifactId>jsr305</artifactId>
+                <version>${version.lib.google-findbugs-jsr305}</version>
             </dependency>
             <!-- END OF Section 3: transitive dependencies we manage the version of for convergence/upgrade -->
 
@@ -1400,6 +1416,28 @@
                 <type>pom</type>
                 <scope>import</scope>
             </dependency>
+            <dependency>
+                <groupId>io.grpc</groupId>
+                <artifactId>grpc-api</artifactId>
+                <version>${version.lib.grpc}</version>
+                <exclusions>
+                    <exclusion>
+                        <groupId>com.google.code.findbugs</groupId>
+                        <artifactId>jsr305</artifactId>
+                    </exclusion>
+                </exclusions>
+            </dependency>
+            <dependency>
+                <groupId>io.grpc</groupId>
+                <artifactId>grpc-protobuf</artifactId>
+                <version>${version.lib.grpc}</version>
+                <exclusions>
+                    <exclusion>
+                        <groupId>com.google.code.findbugs</groupId>
+                        <artifactId>jsr305</artifactId>
+                    </exclusion>
+                </exclusions>
+            </dependency>
             <dependency>
                 <groupId>com.oracle.database.jdbc</groupId>
                 <artifactId>ojdbc-bom</artifactId>

docs/src/main/asciidoc/mp/telemetry.adoc

@@ -1,6 +1,6 @@
 ///////////////////////////////////////////////////////////////////////////////
 
-    Copyright (c) 2023, 2025 Oracle and/or its affiliates.
+    Copyright (c) 2023, 2026 Oracle and/or its affiliates.
 
     Licensed under the Apache License, Version 2.0 (the "License");
     you may not use this file except in compliance with the License.
@@ -49,7 +49,7 @@ include::{rootdir}/includes/dependencies.adoc[]
 ----
 
 [[otel-exporter-dependencies]]
-Also, add a dependency on an OpenTelemetry exporter.
+Microprofile Telemetry mandates that implementations such as Helidon use OpenTelemetry, so also add a dependency on an OpenTelemetry exporter.
 [source,xml]
 .Example dependency for the OpenTelemetry OTLP exporter
 ----
@@ -58,23 +58,14 @@ Also, add a dependency on an OpenTelemetry exporter.
     <artifactId>opentelemetry-exporter-otlp</artifactId>
 </dependency>
 ----
-[source,xml]
-.Example dependency for the OpenTelemetry Jaeger exporter
-----
-<dependency>
-    <groupId>io.opentelemetry</groupId>
-    <artifactId>opentelemetry-exporter-jaeger</artifactId>
-</dependency>
-----
-
-Typical applications use a single exporter but you can add dependencies on multiple exporters and then use configuration to choose which to use in any given execution.
-See the <<Configuration,configuration>> section for more details.
 
 == Usage
 
 link:https://opentelemetry.io/[OpenTelemetry] comprises a collection of APIs, SDKs, integration tools, and other software components intended to facilitate the generation and control of telemetry data, including traces, metrics, and logs. In an environment where distributed tracing is enabled via OpenTelemetry (which combines OpenTracing and OpenCensus), this specification establishes the necessary behaviors for MicroProfile applications to participate seamlessly.
 
-MicroProfile Telemetry {mp-telemetry-version} allows for the exportation of the data it collects to Jaeger or Zipkin and to other systems using a variety of exporters.
+MicroProfile Telemetry {mp-telemetry-version} allows for the export of the data it collects to  other systems using a variety of exporters such as OTLP mentioned earlier. Typical applications use a single exporter but you can add dependencies on multiple exporters and then use configuration to choose which to use in any given execution.
+See the <<Configuration,configuration>> section for more details.
+
 
 // @Deprecated(forRemoval = true) In 5.x remove the following note.
 [NOTE]
@@ -264,7 +255,7 @@ Please consult with the links above for all configurations' properties usage.
 
 For your application to report trace information be sure you add a dependency on an OpenTelemetry exporter as  <<otel-exporter-dependencies,described earlier>> and, as needed, configure its use.
 By default OpenTelemetry attempts to use the OTLP exporter so you do not need to add configuration to specify that choice.
-To use a different exporter set `otel.traces.exporter` in your configuration to the appropriate value: `jaeger`, `zipkin`, `prometheus`, etc.
+To use a different exporter set `otel.traces.exporter` in your configuration to the appropriate value: `zipkin`, `prometheus`, etc.
 See the <<examples,examples>> section below.
 
 === OpenTelemetry Java Agent
@@ -278,13 +269,13 @@ This way, Helidon will explicitly get all the configuration and objects from the
 [[examples]]
 == Examples
 
-This guide demonstrates how to incorporate MicroProfile Telemetry into Helidon and provides illustrations of how to view traces. Jaeger is employed in all the examples, and the Jaeger UI is used to view the traces.
+This guide demonstrates how to incorporate MicroProfile Telemetry into Helidon and provides illustrations of how to view traces. The Jaeger backend is employed in all the examples, and the Jaeger UI is used to view the traces.
 
-=== Set Up Jaeger
+=== Set Up Jaeger Backend
 
-For example, Jaeger will be used for gathering of the tracing information.
+For example, the Jaeger backend gathers the tracing information.
 
-.Run Jaeger in a docker container.
+.Run the Jaeger backend in a docker container
 [source, bash]
 ----
 docker run -d --name jaeger \

docs/src/main/asciidoc/se/guides/tracing.adoc

@@ -1,6 +1,6 @@
 ///////////////////////////////////////////////////////////////////////////////
 
-    Copyright (c) 2019, 2024 Oracle and/or its affiliates.
+    Copyright (c) 2019, 2026 Oracle and/or its affiliates.
 
     Licensed under the Apache License, Version 2.0 (the "License");
     you may not use this file except in compliance with the License.
@@ -58,7 +58,7 @@ Spans are automatically created by Helidon as needed during execution of the RES
 == Getting Started with Tracing
 
 The examples in this guide demonstrate how to integrate tracing with Helidon, how to view traces, how to trace
-across multiple services, and how to integrate tracing with Kubernetes. All examples use Jaeger and traces
+across multiple services, and how to integrate tracing with Kubernetes. All examples use the Jaeger backend and traces
 will be viewed using the Jaeger UI.
 
 === Create a Sample Helidon SE Project
@@ -85,10 +85,10 @@ cd helidon-quickstart-se
 
 === Set up Jaeger
 
-First, you need to run the Jaeger tracer.  Helidon will communicate with this tracer at runtime.
+First, run the Jaeger backend. Helidon communicates with this backend at runtime.
 
 [source,bash]
-.Run Jaeger within a docker container, then check the Jaeger server working:
+.Run Jaeger within a docker container
 ----
 docker run -d --name jaeger \ # <1>
   -e COLLECTOR_OTLP_ENABLED=true \
@@ -109,9 +109,9 @@ docker run -d --name jaeger \ # <1>
 
 === Enable Tracing in the Helidon Application
 
-Update the `pom.xml` file and add the following Jaeger dependency to the `<dependencies>`
-section (*not* `<dependencyManagement>`). This will enable Helidon to use Jaeger at the
-default host and port, `localhost:14250`.
+Update the `pom.xml` file and add the following OpenTelemetry dependency to the `<dependencies>`
+section (*not* `<dependencyManagement>`). This will enable Helidon to use OpenTelemetry at the
+default host and port, `localhost:4317`.
 
 [source,xml]
 .Add the following dependencies to `pom.xml`:
@@ -128,25 +128,23 @@ default host and port, `localhost:14250`.
      </dependency>
      <dependency>
          <groupId>io.helidon.tracing.providers</groupId>
-         <artifactId>helidon-tracing-providers-jaeger</artifactId>  <!--3-->
+         <artifactId>helidon-tracing-providers-opentelemetry</artifactId>  <!--3-->
          <scope>runtime</scope>
      </dependency>
 </dependencies>
 ----
 <1> Helidon Tracing dependencies.
 <2> Observability features for tracing.
-<3> Jaeger tracing provider.
+<3> OpenTelemetry tracing provider.
 
-All spans sent by Helidon to Jaeger need to be associated with a service, assigned by the `tracing.service` setting in the example below.
+Helidon offers several tracing providers: OpenTelemetry, Zipkin, and Jaeger (deprecated).
+All spans sent by Helidon to the backend need to be associated with a service, assigned by the `tracing.service` setting in the example below.
 
 [source,bash]
 .Add the following lines to `src/main/resources/application.yaml`:
 ----
 tracing:
   service: helidon-se-1
-  protocol: http
-  port: 14250
-  path: /api/traces
   tags:
     env: development
   enabled: true
@@ -177,7 +175,7 @@ curl http://localhost:8080/greet
 
 === Viewing Traces Using the Jaeger UI
 
-Jaeger provides a web-based UI at http://localhost:16686 where you can see a visual
+The Jaeger backend provides a web-based UI at http://localhost:16686 where you can see a visual
 representation of the traces and spans within them.
 
 . From the `Service` drop list select `helidon-se-1`. This name corresponds to the `tracing.service` setting you assigned in the `application.yaml` config file.
@@ -252,8 +250,8 @@ Note the row for `mychildSpan`--the custom span created by the added code.
 
 === Using Tracing Across Services
 
-Helidon automatically traces across services if the services use the same tracer, for example, the same instance of Jaeger.
-This means a single trace can include spans from multiple services and hosts.  Helidon uses a `SpanContext` to
+Helidon automatically traces across services if the services propagate span information.
+This means a single trace can include spans from multiple services and hosts. Helidon uses a `SpanContext` to
 propagate tracing information across process boundaries.  When you make client API calls, Helidon will
 internally call OpenTelemetry APIs or OpenTracing APIs to propagate the `SpanContext`. There is nothing you need to do in your application to make this work.
 
@@ -296,14 +294,14 @@ cd helidon-quickstart-se-2
      </dependency>
      <dependency>
          <groupId>io.helidon.tracing.providers</groupId>
-         <artifactId>helidon-tracing-providers-jaeger</artifactId>  <!--3-->
+         <artifactId>helidon-tracing-providers-opentelemetry</artifactId>  <!--3-->
          <scope>runtime</scope>
      </dependency>
 </dependencies>
 ----
 <1> Helidon Tracing API.
 <2> Observability features for tracing.
-<3> Jaeger tracing provider.
+<3> OpenTelemetry tracing provider.
 
 [source,bash]
 .Replace `src/main/resources/application.yaml` with the following:
@@ -313,9 +311,6 @@ app:
 
 tracing:
   service: helidon-se-2
-  protocol: http
-  port: 14250
-  path: /api/traces
   tags:
     env: development
   enabled: true

microprofile/grpc/client/pom.xml

@@ -61,6 +61,10 @@
             <groupId>jakarta.enterprise</groupId>
             <artifactId>jakarta.enterprise.cdi-api</artifactId>
         </dependency>
+        <dependency>
+            <groupId>com.google.code.findbugs</groupId>
+            <artifactId>jsr305</artifactId>
+        </dependency>
         <dependency>
             <groupId>io.helidon.webserver</groupId>
             <artifactId>helidon-webserver-grpc</artifactId>

tracing/exporter-jaeger/README.md

@@ -0,0 +1,12 @@
+# Helidon's Jaeger Tracing Exporter
+
+Both Jaeger and OpenTelemetry have eliminated their support for _sending_ tracing span data from monitored servers using the Jaeger tracing protocol. That said, many backend products (including Jaeger's) continue to accept input in this way.
+
+The Helidon Jaeger tracing exporter offers a _temporary_ bridge so applications can continue to send data to backends using the Jaeger protocol while their developers work on migrating to another exporter.
+
+Helidon SE applications adopting Helidon 4.4.0 can continue--in the _short term_--to depend on `io.helidon.tracing:helidon-tracing-providers-jaeger` (also deprecated). That provider now depends on this component to send data using the Jaeger protocol. 
+
+Helidon MP applications adopting Helidon 4.4.0 must remove any dependency on OpenTelemetry's `opentelemetry-exporter-jaeger` component; it no longer exists. Replace those dependencies with a dependency on this component, `io.helidon.tracing:helidon-tracing-exporter-jaeger`.
+
+# Deprecation
+Note that both this Jaeger exporter and Helidon's Jaeger tracing provider are deprecated and are likely to be removed in a future major Helidon release.

tracing/exporter-jaeger/etc/spotbugs/exclude.xml

@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!--
+    Copyright (c) 2026 Oracle and/or its affiliates.
+
+    Licensed under the Apache License, Version 2.0 (the "License");
+    you may not use this file except in compliance with the License.
+    You may obtain a copy of the License at
+
+        http://www.apache.org/licenses/LICENSE-2.0
+
+    Unless required by applicable law or agreed to in writing, software
+    distributed under the License is distributed on an "AS IS" BASIS,
+    WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+    See the License for the specific language governing permissions and
+    limitations under the License.
+  -->
+
+<FindBugsFilter
+        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+        xmlns="https://github.com/spotbugs/filter/3.0.0"
+        xsi:schemaLocation="https://github.com/spotbugs/filter/3.0.0 https://raw.githubusercontent.com/spotbugs/spotbugs/3.1.0/spotbugs/etc/findbugsfilter.xsd">
+
+    <!-- These violations are in generated code. -->
+    <Match>
+        <Class name="io.helidon.tracing.exporter.jaeger.proto.api_v2.Model$Span" />
+        <Bug pattern="SE_BAD_FIELD" />
+    </Match>
+    <Match>
+        <Class name="io.helidon.tracing.exporter.jaeger.proto.api_v2.Model$Trace" />
+        <Bug pattern="SE_BAD_FIELD" />
+    </Match>
+</FindBugsFilter>