This is an automated email from the ASF dual-hosted git repository.

jamesnetherton pushed a commit to branch 2.13.x
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git


The following commit(s) were added to refs/heads/2.13.x by this push:
     new 1770f675f3 Added conditional logic for supported content.
1770f675f3 is described below

commit 1770f675f3a51a52f37291616dfb287793675d16
Author: Gerry Forde <gfo...@gforde.remote.csb>
AuthorDate: Mon Jan 9 22:33:33 2023 +0000

    Added conditional logic for supported content.
---
 docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc | 9 +++++++--
 extensions/opentelemetry/runtime/src/main/doc/usage.adoc        | 9 +++++++--
 2 files changed, 14 insertions(+), 4 deletions(-)

diff --git a/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc 
b/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
index a9a4a1eebf..5eb7e0d2fe 100644
--- a/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
+++ b/docs/modules/ROOT/pages/reference/extensions/opentelemetry.adoc
@@ -62,8 +62,11 @@ 
quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:4317
 quarkus.opentelemetry.tracer.exporter.jaeger.endpoint=http://localhost:14250
 ----
 
-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).
+Note that you must add a dependency to the OpenTelemetry exporter that you 
want to work with. 
+
+ifeval::[{doc-show-advanced-features} == true]
+
+At present, Quarkus has support for Jaeger and the OpenTelemetry Protocol 
Specification (OTLP).
 
 For Jaeger:
 
@@ -84,6 +87,8 @@ For OTLP:
 </dependency>
 ----
 
+endif::[]
+
 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.
 
 Route endpoints can be excluded from tracing by configuring a property named 
`quarkus.camel.opentelemetry.exclude-patterns` in `application.properties`. For 
example:
diff --git a/extensions/opentelemetry/runtime/src/main/doc/usage.adoc 
b/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
index 7a15c85039..01842728b8 100644
--- a/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
+++ b/extensions/opentelemetry/runtime/src/main/doc/usage.adoc
@@ -14,8 +14,11 @@ 
quarkus.opentelemetry.tracer.exporter.otlp.endpoint=http://localhost:4317
 quarkus.opentelemetry.tracer.exporter.jaeger.endpoint=http://localhost:14250
 ----
 
-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).
+Note that you must add a dependency to the OpenTelemetry exporter that you 
want to work with. 
+
+ifeval::[{doc-show-advanced-features} == true]
+
+At present, Quarkus has support for Jaeger and the OpenTelemetry Protocol 
Specification (OTLP).
 
 For Jaeger:
 
@@ -36,6 +39,8 @@ For OTLP:
 </dependency>
 ----
 
+endif::[]
+
 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.
 
 Route endpoints can be excluded from tracing by configuring a property named 
`quarkus.camel.opentelemetry.exclude-patterns` in `application.properties`. For 
example:

Reply via email to