GitHub grafana/loki Like Prometheus but for logs

GitHub – grafana/loki: Like Prometheus, but for logs.

Best Online Casinos


1. Sol Casino

Sol casino keyword

Free Sign-Up Bonus: 80 Free Spins ( Free Sign-Up Bonus Link )


First Deposit Bonus: 150% up to €/$ 200 ( Registration Link )





2. Fresh Casino

fresh casino

Free Sign-Up Bonus: 70 Free Spins ( Free Sign-Up Bonus Link )


First Deposit Bonus: 200% up to €/$ 1000 ( Registration Link )






3. Jet Casino

jet casino

Free Sign-Up Bonus: 90 Free Spins ( Free Sign-Up Bonus Link )


First Deposit Bonus: 150% up to €/$ 300 ( Registration Link )







GitHub – grafana/loki: Like Prometheus, but for logs.

Loki Logo

Drone CI' data-canonical-src='
Go Report Card' data-canonical-src='
Slack' data-canonical-src='
Fuzzing Status' data-canonical-src='

Loki: like Prometheus, but for logs.

Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream.

Compared to other log aggregation systems, Loki:

  • does not do full text indexing on logs. By storing compressed, unstructured logs and only indexing metadata, Loki is simpler to operate and cheaper to run.
  • indexes and groups log streams using the same labels you’re already using with Prometheus, enabling you to seamlessly switch between metrics and logs using the same labels that you’re already using with Prometheus.
  • is an especially good fit for storing Kubernetes Pod logs. Metadata such as Pod labels is automatically scraped and indexed.
  • has native support in Grafana (needs Grafana v6.0).

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.
  • Grafana for querying and displaying the logs.

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 focusing on logs instead of metrics, and delivering logs via push, instead of pull.

Getting started

  • Installing Loki
  • Installing Promtail
  • Getting Started


  • Upgrading Loki


  • Latest release
  • Upcoming release, at the tip of the main branch

Commonly used sections:

  • API documentation for getting logs into Loki.
  • Labels
  • Operations
  • Promtail is an agent which tails log files and pushes them to Loki.
  • Pipelines details the log processing pipeline.
  • Docker Driver Client is a Docker plugin to send logs directly to Loki from Docker containers.
  • LogCLI provides a command-line interface for querying logs.
  • Loki Canary monitors your Loki installation for missing logs.
  • Troubleshooting presents help dealing with error messages.
  • Loki in Grafana describes how to set up a Loki datasource in Grafana.

Getting Help

If you have any questions or feedback regarding Loki:

  • Search existing thread in the Grafana Labs community forum for Loki:
  • Ask a question on the Loki Slack channel. To invite yourself to the Grafana Slack, visit and join the #loki channel.
  • File an issue for bugs, issues and feature suggestions.
  • Send an email to [email protected], or use the web interface.
  • UI issues should be filed directly in Grafana.

Your feedback is always welcome.

Further Reading

  • The original design doc for Loki is a good source for discussion of the motivation and design decisions.
  • Callum Styan’s March 2019 DevOpsDays Vancouver talk “Grafana Loki: Log Aggregation for Incident Investigations”.
  • Grafana Labs blog post “How We Designed Loki to Work Easily Both as Microservices and as Monoliths”.
  • Tom Wilkie’s early-2019 CNCF Paris/FOSDEM talk “Grafana Loki: like Prometheus, but for logs” (slides, video).
  • David Kaltschmidt’s KubeCon 2018 talk “On the OSS Path to Full Observability with Grafana” (slides, video) on how Loki fits into a cloud-native environment.
  • Goutham Veeramachaneni’s blog post “Loki: Prometheus-inspired, open source logging for cloud natives” on details of the Loki architecture.
  • David Kaltschmidt’s blog post “Closer look at Grafana’s user interface for Loki” on the ideas that went into the logging user interface.


Refer to

Building from source

Loki can be run in a single host, no-dependencies mode using the following commands.

You need go, we recommend using the version found in our build Dockerfile

$ go get $ cd $GOPATH/src/ # GOPATH is $HOME/go by default.
$ go build ./cmd/loki $ ./loki -config.file=./cmd/loki/loki-local-config.yaml …

To build Promtail on non-Linux platforms, use the following command:

$ go build ./clients/cmd/promtail

On Linux, Promtail requires the systemd headers to be installed if Journal support is enabled. To enable Journal support the go build tag flag promtail_journal_enabled should be passed

With Journal support on Ubuntu, run with the following commands:

$ sudo apt install -y libsystemd-dev $ go build ./clients/cmd/promtail –tags=promtail_journal_enabled

With Journal support on CentOS, run with the following commands:

$ sudo yum install -y systemd-devel $ go build ./clients/cmd/promtail –tags=promtail_journal_enabled

Otherwise, to build Promtail without Journal support, run go build
with CGO disabled:

$ CGO_ENABLED=0 go build ./clients/cmd/promtail


Please see for some of the organizations using Loki today. If you would like to add your organization to the list, please open a PR to add it to the list.


Grafana Loki is distributed under AGPL-3.0-only. For Apache-2.0 exceptions, see