docs(observability): fix relative image links (#489)

cloudoperators · Nov 11, 2024 · 12e3e65 · 12e3e65
1 parent 6831b78
commit 12e3e65
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/alerts/README.md b/alerts/README.md
@@ -18,7 +18,7 @@ Components included in this Plugin:
 
 This Plugin usually is deployed along the **kube-monitoring** Plugin and does not deploy the [Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator) itself. However, if you are intending to use it stand-alone, you need to explicitly enable the deployment of Prometheus Operator, otherwise it will not work. It can be done in the configuration interface of the plugin.
 
-![Alerts Plugin Architecture](./img/Alerts-arch.png)
+![Alerts Plugin Architecture](img/Alerts-arch.png)
 
 ## Disclaimer
 

diff --git a/kube-monitoring/README.md b/kube-monitoring/README.md
@@ -12,7 +12,7 @@ Observability is often required for operation and automation of service offering
 
 This Plugin includes a pre-configured package of components that help make getting started easy and efficient. At its core, an automated and managed _Prometheus_ installation is provided using the _prometheus-operator_. This is complemented by Prometheus target configuration for the most common Kubernetes components providing metrics by default. In addition, [Cloud operators](https://github.com/cloudoperators/kubernetes-operations) curated _Prometheus_ alerting rules and _Plutono_ dashboards are included to provide a comprehensive monitoring solution out of the box. 
 
-![kube-monitoring](./img/kube-monitoring-setup.png)
+![kube-monitoring](img/kube-monitoring-setup.png)
 
 Components included in this Plugin:
 

diff --git a/plutono/README.md b/plutono/README.md
@@ -10,7 +10,7 @@ The main terminologies used in this document can be found in [core-concepts](htt
 
 Observability is often required for the operation and automation of service offerings. Plutono provides you with tools to display Prometheus metrics on live dashboards with insightful charts and visualizations. In the Greenhouse context, this complements the **kube-monitoring** plugin, which automatically acts as a Plutono data source which is recognized by Plutono. In addition, the Plugin provides a mechanism that automates the lifecycle of datasources and dashboards without having to restart Plutono.
 
-![Plutono Architecture](./img/Plutono-arch.png)
+![Plutono Architecture](img/Plutono-arch.png)
 
 ## Disclaimer
 

diff --git a/thanos/README.md b/thanos/README.md
@@ -10,7 +10,7 @@ The main terminologies used in this document can be found in [core-concepts](htt
 
 Thanos is a set of components that can be used to extend the storage and retrieval of metrics in Prometheus. It allows you to store metrics in a remote object store and query them across multiple Prometheus servers and Greenhouse clusters. This Plugin is intended to provide a set of pre-configured Thanos components that enable a proven composition. At the core, a set of Thanos components is installed that adds long-term storage capability to a single **kube-monitoring** Plugin and makes both current and historical data available again via one Thanos Query component.
 
-![Thanos Architecture](./img/Thanos-setup-example.png)
+![Thanos Architecture](img/Thanos-setup-example.png)
 
 The **Thanos Sidecar** is a component that is deployed as a container together with a Prometheus instance. This allows Thanos to optionally upload metrics to the object store and Thanos Query to access Prometheus data via a common, efficient StoreAPI.
 
@@ -141,7 +141,7 @@ If you just have one occurence of this Thanos plugin dpeloyed, the default optio
 
 ### Standalone Query
 
-![Standalone Query](./img/Thanos-standalone-query.png)
+![Standalone Query](img/Thanos-standalone-query.png)
 
 In case you want to achieve a setup like above and have an overarching Thanos Query to run with multiple Stores, you can set it to `standalone` and add your own store list. Setup your Plugin like this: