Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docs: fix pic location in `sources/fundamentals/architecture/deployme… #6089

Merged
merged 1 commit into from
May 4, 2022
Merged

Docs: fix pic location in `sources/fundamentals/architecture/deployme… #6089

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/sources/fundamentals/architecture/deployment-modes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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`.
Expand Down Expand Up @@ -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.
Expand Down