Fix images path

Gemfile.lock

@@ -122,6 +122,8 @@ GEM
       sass-embedded (~> 1.54)
     jekyll-seo-tag (2.8.0)
       jekyll (>= 3.8, < 5.0)
+    jekyll-sitemap (1.4.0)
+      jekyll (>= 3.7, < 5.0)
     jekyll-watch (2.2.1)
       listen (~> 3.0)
     just-the-docs (0.5.4)
@@ -241,6 +243,7 @@ DEPENDENCIES
   jekyll (~> 4.3.2)
   jekyll-feed (~> 0.12)
   jekyll-redirect-from
+  jekyll-sitemap
   just-the-docs
   minima (~> 2.5)
   octokit

using-gatewayd/observability.md

@@ -19,7 +19,7 @@ The configuration parameters for [logging](global-configuration/loggers) and [me
 
 GatewayD supports multiple loggers. Each logger can send logs to multiple outputs, including console, stdout, stderr, file, Syslog and Rsyslog. The loggers generate structured logs, which can be easily parsed by log aggregators such as [fluentbit](https://fluentbit.io/). The log messages are also human-readable, as shown in the example below.
 
-![Logs in console](assets/console-log.png)
+![Logs in console](/using-gatewayd/assets/console-log.png)
 
 Logs generated by the plugins are aggregated by GatewayD and sent to the loggers with an extra key/value field, for example `plugin=gatewayd-plugin-cache`, so that they can be filtered out for analysis.
 
@@ -31,7 +31,7 @@ The log level of GatewayD affects the aggregation of logs from the plugins. For
 
 Metrics are exposed from GatewayD and the plugins in Prometheus format. GatewayD collects, relabels and merges Prometheus metrics from all the plugins and exposes them over `http://localhost:9090/metrics` by default, which is [configurable](global-configuration/metrics#configuration-parameters). List of built-in metrics are available [here](global-configuration/metrics#built-in-metrics).
 
-![Metrics](assets/prometheus.png)
+![Metrics](/using-gatewayd/assets/prometheus.png)
 
 Metrics generated by the plugins are aggregated by GatewayD and exposed over the Unix Domain Socket, so that the *metrics merger* can read them, relabel them with an extra label, for example `plugin=gatewayd_plugin_cache` and merged with the metrics of GatewayD. The extra label is added, so that the plugins metrics can be filtered out for analysis.
 
@@ -41,7 +41,7 @@ Plugins can choose to expose metrics to GatewayD. The metrics merger can be conf
 
 Tracing can be enabled from the CLI. Once enabled, GatewayD will send traces in OpenTelemetry format via gRPC to supported backends, such as [Jaeger](https://www.jaegertracing.io/) and [Grafana Tempo](https://grafana.com/oss/tempo/).
 
-![Traces](assets/jaeger.png)
+![Traces](/using-gatewayd/assets/jaeger.png)
 
 Currently the traces are generated for the following events and they are all grouped under the `GatewayD` service: