This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch 2.14.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/2.14.x by this push:
new 8c5f39b4bb Update OpenTelemetry exporter documentation in line with
changes in Quarkus 2.14.0.Final
8c5f39b4bb is described below
commit 8c5f39b4bbd78f522f2640ba339730a831fe1d27
Author: James Netherton <[email protected]>
AuthorDate: Mon Nov 7 08:31:43 2022 +0000
Update OpenTelemetry exporter documentation in line with changes in Quarkus
2.14.0.Final
---
.../pages/reference/extensions/opentelemetry.adoc | 32 ++++----------------
.../opentelemetry/runtime/src/main/doc/usage.adoc | 34 +++++-----------------
2 files changed, 13 insertions(+), 53 deletions(-)
diff --git a/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
b/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
index 5d1dce8a48..ed13a1e722 100644
--- a/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
@@ -55,33 +55,8 @@ In order to send the captured traces to a tracing system,
you need to configure
# Identifier for the origin of spans created by the application
quarkus.application.name=my-camel-application
-# For OTLP
+# OTLP exporter endpoint
quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:55680
-
-# For Jaeger
-quarkus.opentelemetry.tracer.exporter.jaeger.endpoint=http://localhost:14268/api/traces
-----
-
-Note that you must add a dependency to the OpenTelemetry exporter that you
want to work with. At present, Quarkus has support for
-Jaeger and the OpenTelemetry Protocol Specification (OTLP).
-
-For Jaeger:
-
-[source,xml]
-----
-<dependency>
- <groupId>io.quarkus</groupId>
- <artifactId>quarkus-opentelemetry-exporter-jaeger</artifactId>
-</dependency>
-----
-
-For OTLP:
-[source,xml]
-----
-<dependency>
- <groupId>io.quarkus</groupId>
- <artifactId>quarkus-opentelemetry-exporter-otlp</artifactId>
-</dependency>
----
Refer to the
https://github.com/quarkusio/quarkus/blob/{quarkus-version}/docs/src/main/asciidoc/opentelemetry.adoc[Quarkus
OpenTelemetry guide] for a full list of configuration options.
@@ -94,6 +69,11 @@ Route endpoints can be excluded from tracing by configuring
a property named `qu
quarkus.camel.opentelemetry.exclude-patterns=direct:*,netty-http:*
----
+### Exporters
+
+Quarkus OpenTelemetry defaults to the standard OTLP exporter defined in
OpenTelemetry.
+Additional exporters will be available in the Quarkiverse
https://github.com/quarkiverse/quarkus-opentelemetry-exporter/blob/main/README.md[quarkus-opentelemetry-exporter]
project.
+
[id="extensions-opentelemetry-additional-camel-quarkus-configuration"]
== Additional Camel Quarkus configuration
diff --git a/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
b/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
index 6fe2e76f20..3f3e2f8010 100644
--- a/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
+++ b/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
@@ -7,33 +7,8 @@ In order to send the captured traces to a tracing system, you
need to configure
# Identifier for the origin of spans created by the application
quarkus.application.name=my-camel-application
-# For OTLP
+# OTLP exporter endpoint
quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:55680
-
-# For Jaeger
-quarkus.opentelemetry.tracer.exporter.jaeger.endpoint=http://localhost:14268/api/traces
-----
-
-Note that you must add a dependency to the OpenTelemetry exporter that you
want to work with. At present, Quarkus has support for
-Jaeger and the OpenTelemetry Protocol Specification (OTLP).
-
-For Jaeger:
-
-[source,xml]
-----
-<dependency>
- <groupId>io.quarkus</groupId>
- <artifactId>quarkus-opentelemetry-exporter-jaeger</artifactId>
-</dependency>
-----
-
-For OTLP:
-[source,xml]
-----
-<dependency>
- <groupId>io.quarkus</groupId>
- <artifactId>quarkus-opentelemetry-exporter-otlp</artifactId>
-</dependency>
----
Refer to the
https://github.com/quarkusio/quarkus/blob/{quarkus-version}/docs/src/main/asciidoc/opentelemetry.adoc[Quarkus
OpenTelemetry guide] for a full list of configuration options.
@@ -44,4 +19,9 @@ Route endpoints can be excluded from tracing by configuring a
property named `qu
----
# Exclude all direct & netty-http endpoints from tracing
quarkus.camel.opentelemetry.exclude-patterns=direct:*,netty-http:*
-----
\ No newline at end of file
+----
+
+### Exporters
+
+Quarkus OpenTelemetry defaults to the standard OTLP exporter defined in
OpenTelemetry.
+Additional exporters will be available in the Quarkiverse
https://github.com/quarkiverse/quarkus-opentelemetry-exporter/blob/main/README.md[quarkus-opentelemetry-exporter]
project.
