[camel-website] 02/11: Update content/blog/2023/03/camel-observation/index.md

[zr...@apache.org]

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

zregvart pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git

commit f96e37265fd35d6a7d3ea31728c1b2ff83fd5c7d
Author: Marcin Grzejszczak <ma...@grzejszczak.pl>
AuthorDate: Mon Apr 3 15:32:17 2023 +0200

    Update content/blog/2023/03/camel-observation/index.md
    
    Co-authored-by: Zoran Regvart <zo...@regvart.com>
---
 content/blog/2023/03/camel-observation/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/blog/2023/03/camel-observation/index.md b/content/blog/2023/03/camel-observation/index.md
index 9439dee1..b11715aa 100644
--- a/content/blog/2023/03/camel-observation/index.md
+++ b/content/blog/2023/03/camel-observation/index.md
@@ -111,7 +111,7 @@ registry.observationConfig().observationHandler(new DefaultTracingObservationHan
 
 ## How does Micrometer Observation work with Camel?
 
-Apache Camel comes with an abstraction of a [`Tracer`](https://camel.apache.org/components/3.20.x/others/tracing.html). It automatically creates spans for Camel Routes.
+Apache Camel comes with an abstraction of a [`Tracer`](/components/3.20.x/others/tracing.html). It automatically creates spans for Camel Routes.
 
 With Micrometer Observation we've modified the concept of a `Tracer` to allow distingushing between high and low cardinality tags. That in turn allowed us to use the `Tracer` API to create `Observations` instead of spans. That allowed us to automatically create both traces and metrics depending on your `ObservationRegistry` setup.