This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/main by this push:
new 0179ebb4ca Fix incorrect exporter endpoint configuration property in
OpenTelemetry extension documentation
0179ebb4ca is described below
commit 0179ebb4ca90d9975da2ea738377a8c331e7d3f3
Author: James Netherton <[email protected]>
AuthorDate: Wed Oct 30 11:27:04 2024 +0000
Fix incorrect exporter endpoint configuration property in OpenTelemetry
extension documentation
---
docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc | 4 ++--
extensions/opentelemetry/runtime/src/main/doc/usage.adoc | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
b/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
index 02c895fcc3..0c69d8cd4d 100644
--- a/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
@@ -56,7 +56,7 @@ In order to send the captured traces to a tracing system, you
need to configure
quarkus.application.name=my-camel-application
# OTLP exporter endpoint
-quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:4317
+quarkus.otel.exporter.otlp.traces.endpoint=http://localhost:4317
----
Refer to the https://quarkus.io/guides/opentelemetry[Quarkus OpenTelemetry
guide] for a full list of configuration options.
@@ -80,7 +80,7 @@ Additional exporters will be available in the Quarkiverse
https://github.com/qua
When instrumenting the execution of CDI bean methods from Camel routes, you
should annotate such methods with
`io.opentelemetry.extension.annotations.WithSpan`. Methods annotated with
`@WithSpan` will create a new Span and establish any required relationships
with the current Trace context.
-For example, to instrument a CDI bean from a Camel route, first ensure the
appropriate methods are annotated with `@WithTrace`.
+For example, to instrument a CDI bean from a Camel route, first ensure the
appropriate methods are annotated with `@WithSpan`.
[source,java]
----
diff --git a/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
b/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
index 80d03b2ce0..649814bd1f 100644
--- a/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
+++ b/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
@@ -8,7 +8,7 @@ In order to send the captured traces to a tracing system, you
need to configure
quarkus.application.name=my-camel-application
# OTLP exporter endpoint
-quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:4317
+quarkus.otel.exporter.otlp.traces.endpoint=http://localhost:4317
----
Refer to the https://quarkus.io/guides/opentelemetry[Quarkus OpenTelemetry
guide] for a full list of configuration options.
@@ -30,7 +30,7 @@ Additional exporters will be available in the Quarkiverse
https://github.com/qua
When instrumenting the execution of CDI bean methods from Camel routes, you
should annotate such methods with
`io.opentelemetry.extension.annotations.WithSpan`. Methods annotated with
`@WithSpan` will create a new Span and establish any required relationships
with the current Trace context.
-For example, to instrument a CDI bean from a Camel route, first ensure the
appropriate methods are annotated with `@WithTrace`.
+For example, to instrument a CDI bean from a Camel route, first ensure the
appropriate methods are annotated with `@WithSpan`.
[source,java]
----
