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

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

commit 3678184370f196e32d0b3ee1d004736e5eb59168
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Wed Jun 9 18:28:38 2021 +0200

    Fixes website build
---
 docs/modules/ROOT/pages/observability/integration-logging.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/modules/ROOT/pages/observability/integration-logging.adoc 
b/docs/modules/ROOT/pages/observability/integration-logging.adoc
index 6c6f877..2efc753 100644
--- a/docs/modules/ROOT/pages/observability/integration-logging.adoc
+++ b/docs/modules/ROOT/pages/observability/integration-logging.adoc
@@ -1,7 +1,7 @@
 [[integration-logging]]
 = Camel K Integration Logging
 
-Starting with 
https://camel.apache.org/blog/2021/05/new-camel-k-logging-features/[Camel K 
1.5], we introduced a new
+Starting with link:/blog/2021/05/new-camel-k-logging-features/[Camel K 1.5], 
we introduced a new
 xref:traits:logging.adoc[logging trait] that simplifies access to the logging 
configuration available on the runtime.
 
 
@@ -33,4 +33,4 @@ A sample custom configuration would look like this:
 
 Like the operator, the integrations will use structured logs to facilitate 
collection and parsing. This can be turned on
 or off using the `--trait logging.json` trait. Subsequently, it can also be 
customized to output pretty json logs by
-setting the `logging.json.pretty-print` trait.
\ No newline at end of file
+setting the `logging.json.pretty-print` trait.

Reply via email to