Skip to content
/ loki Public
forked from grafana/loki

Like Prometheus, but for logs.

License

Notifications You must be signed in to change notification settings

arcosx/loki

This branch is 4823 commits behind grafana/loki:main.

Folders and files

NameName
Last commit message
Last commit date
Aug 15, 2022
Aug 15, 2022
Aug 3, 2022
Aug 26, 2022
Aug 26, 2022
Oct 8, 2019
Aug 26, 2022
Jul 18, 2022
Aug 12, 2022
Aug 26, 2022
Aug 24, 2022
Aug 26, 2022
Aug 26, 2022
Aug 26, 2022
Aug 25, 2022
Jul 20, 2022
Jan 11, 2022
Jun 15, 2022
Jun 30, 2022
Apr 22, 2022
May 12, 2021
May 25, 2022
Aug 26, 2022
Jul 27, 2020
Nov 4, 2020
Apr 20, 2021
Jun 6, 2022
Jun 27, 2022
Aug 15, 2022
Mar 9, 2022
Feb 6, 2020
Aug 25, 2022
Aug 25, 2022
Sep 6, 2019

Repository files navigation

Loki Logo

Drone CI CircleCI Go Report Card Slack Fuzzing Status

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

Upgrading

Documentation

Commonly used sections:

Getting Help

If you have any questions or feedback regarding Loki:

Your feedback is always welcome.

Further Reading

Contributing

Refer to CONTRIBUTING.md

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 github.com/grafana/loki
$ cd $GOPATH/src/github.com/grafana/loki # 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 for Journal support.

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

$ sudo apt install -y libsystemd-dev
$ go build ./clients/cmd/promtail

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

$ sudo yum install -y systemd-devel
$ go build ./clients/cmd/promtail

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

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

Adopters

Please see ADOPTERS.md 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.

License

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

About

Like Prometheus, but for logs.

Resources

License

Code of conduct

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 94.0%
  • Jsonnet 2.6%
  • Ruby 0.7%
  • Makefile 0.6%
  • Shell 0.5%
  • Yacc 0.4%
  • Other 1.2%