You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by pc...@apache.org on 2023/07/25 12:11:24 UTC

[camel-website] branch main updated: fix(doc): Info on namespace limitation on auto trait

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-website.git


The following commit(s) were added to refs/heads/main by this push:
     new f88ba6e9 fix(doc): Info on namespace limitation on auto trait
f88ba6e9 is described below

commit f88ba6e99f7353f941d0a80949e20b4878914277
Author: Gaelle Fournier <ga...@gmail.com>
AuthorDate: Mon Jul 17 10:18:06 2023 +0200

    fix(doc): Info on namespace limitation on auto trait
---
 content/blog/2023/03/camel-k-telemetry/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2023/03/camel-k-telemetry/index.md b/content/blog/2023/03/camel-k-telemetry/index.md
index 9546bd0c..e7c62470 100644
--- a/content/blog/2023/03/camel-k-telemetry/index.md
+++ b/content/blog/2023/03/camel-k-telemetry/index.md
@@ -307,7 +307,7 @@ This configuration will:
 
 We are also using inventory.local and order.local host in ingress for the rest services so make sure that your DNS pointing to your cluster for both hostnames. You can execute `echo "$(minikube ip) order.local inventory.local" | sudo tee -a /etc/hosts` if you are working on minikube.
 
-As you can see we did not provide the OTLP API endpoint as Camel K automatically discovered the **Jaeger** OTLP API endpoint. For any other Distributed Tracing tool you will have to declare it through `-t telemetry.endpoint=xxxx`. The `telemetry` trait is expecting an [OTLP trace endpoint](https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/#otel_exporter_otlp_traces_endpoint).
+As you can see we did not provide the OTLP API endpoint as Camel K automatically discovered the **Jaeger** OTLP API endpoint available in the namespace. For any other Distributed Tracing tool you will have to declare it through `-t telemetry.endpoint=xxxx`. The `telemetry` trait is expecting an [OTLP trace endpoint](https://opentelemetry.io/docs/concepts/sdk-configuration/otlp-exporter-configuration/#otel_exporter_otlp_traces_endpoint).
 
 Now that everything is up let's make some traces!