From f6c483e2c189c549088908025eff05e47bb7e202 Mon Sep 17 00:00:00 2001 From: Tom Wilkie <tomwilkie@users.noreply.github.com> Date: Tue, 18 Dec 2018 15:34:27 +0000 Subject: [PATCH] Clarify what we mean by 'like Prometheus, but for logs'. (#149) * Clarify what we mean by 'like Prometheus, but for logs'. Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com> * Typos. Signed-off-by: Tom Wilkie <tom.wilkie@gmail.com> --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index fc824114..f5e4be0a 100644 --- a/README.md +++ b/README.md @@ -17,10 +17,13 @@ Compared to other log aggregation systems, Loki: A Loki-based logging stack consists of 3 components: +- `promtail` is the agent, responsible for gathering logs and sending them to Loki. - `loki` is the main server, responsible for storing logs and processing queries. -- `promtail` is the agent, responsible for gathering logs and sending them to loki. - [Grafana](https://github.com/grafana/grafana) for the UI. +Loki is like Prometheus, but for logs: we prefer a multidimensional label-based approach to indexing, and want a single-binary, easy to operate system with no dependencies. +Loki differs from Prometheus by focussing on logs instead of metrics, and deliverying logs via push, instead of pull. + ## Getting started For instructions on getting started with Loki, see [our getting started docs](./production/README.md). -- GitLab