|
|
|
@ -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 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. |
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
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 |
|
|
|
|
|
|
|
|
|
 |
|
|
|
|
 |
|
|
|
|
|
|
|
|
|
Running components as individual microservices allows scaling up |
|
|
|
|
by increasing the quantity of microservices. |
|
|
|
|