logs

Read-Write mode (读写模式) - Logs

The read-write mode provides an alternative to monolithic and microservices modes.

In read-write mode, components are grouped into three services to ease the operational overhead whilst still allowing scale to be tuned separately on the read and write paths. The services group the components as follows:

• read
  • query-frontend
  • querier
• backend
  • ruler
• write
  • distributor
  • ingester

Similar to the other modes, each Grafana Mimir process is invoked with its -target parameter set to the specific service: -target=read, -target=write, or -target=backend.

Diagram

The below diagram describes the various components of this deployment, and how data flows between them.

flowchart LR
    A  -->|writes| GW  -->|writes| D   -->|writes| I  -->|writes| M
    G -.->|reads | GW -.->|reads | QF -.->|reads | Q -.->|reads | M

    subgraph Minio
        M{"Object Storage"}
    end
    subgraph Agent["Grafana Alloy"]
        A("alloy")
    end
    subgraph Grafana
        G("grafana")
    end
    subgraph Gateway["Load Balancer"]
        GW{"Nginx"}
    end

    subgraph LokiWrite["loki -target=write"]
        I("ingester")
        D("distributor")
    end
    subgraph LokiRead["loki -target=read"]
        Q("querier")
        QF("query-frontend")
    end

Loading

Quick Start

Install dependencies tools

git clone https://github.com/qclaogui/codelab-monitoring.git && cd "$(basename "$_" .git)"

make install-build-deps

Create a cluster and mapping the ingress port 80 to localhost:8080

make cluster

Deploy manifests

make deploy-read-write-mode-logs

Once all containers are up and running you can search for logs in Grafana.

Navigate to http://localhost:8080/explore and select the search tab.

Clean up

make delete-read-write-mode-logs