From fd077f8b218e2c406ebca6dc37349bb9fab8e9ba Mon Sep 17 00:00:00 2001 From: n4mine Date: Tue, 3 May 2022 21:57:43 +0800 Subject: [PATCH] Docs: fix pic location in `sources/fundamentals/architecture/deployment-modes.md` --- docs/sources/fundamentals/architecture/deployment-modes.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/sources/fundamentals/architecture/deployment-modes.md b/docs/sources/fundamentals/architecture/deployment-modes.md index 151d31a7cd33..9055fc24b07b 100644 --- a/docs/sources/fundamentals/architecture/deployment-modes.md +++ b/docs/sources/fundamentals/architecture/deployment-modes.md @@ -28,7 +28,7 @@ This is monolithic mode; it runs all of Loki’s microservice components inside a single process as a single binary or Docker image. -![monolithic mode diagram](../monolithic-mode.png) +![monolithic mode diagram](./monolithic-mode.png) Monolithic mode is useful for getting started quickly to experiment with Loki, as well as for small read/write volumes of up to approximately 100GB per day. @@ -54,7 +54,7 @@ Loki provides the simple scalable deployment mode. This deployment mode can scale to several TBs of logs per day and more. Consider the microservices mode approach for very large Loki installations. -![simple scalable deployment mode diagram](../simple-scalable.png) +![simple scalable deployment mode diagram](./simple-scalable.png) In this mode the component microservices of Loki are bundled into two targets: `-target=read` and `-target=write`. @@ -89,7 +89,7 @@ Each process is invoked specifying its `target`: * ruler * compactor -![microservices mode diagram](../microservices-mode.png) +![microservices mode diagram](./microservices-mode.png) Running components as individual microservices allows scaling up by increasing the quantity of microservices.