Like Prometheus, but for logs.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Edward Welch 42e5bf1af8 need to remove this return statement or positions will never be cleaned up 6 years ago
.circleci Adding a specific ssh key fingerprint to use for pushing back to loki repo 6 years ago
.github/ISSUE_TEMPLATE Added question template 6 years ago
cmd Take 2 for fix the limit settings (#519) 6 years ago
docs Fix typo in example config (#530) 6 years ago
fluentd/fluent-plugin-loki Merge pull request #397 from cosmo0920/fluent-plugin-documentation 6 years ago
loki-build-image Setup Helm chart repository 6 years ago
pkg need to remove this return statement or positions will never be cleaned up 6 years ago
production Add option (#528) 6 years ago
tools Remove liveness probes from promtail 6 years ago
vendor vendor: update cortex (#512) 6 years ago
.gitignore Separate loki & promtail charts 6 years ago
.gometalinter.json [WIP] Persistence (#44) 7 years ago
CONTRIBUTING.md Expand documentation (#261) 6 years ago
Gopkg.lock vendor: update cortex (#512) 6 years ago
Gopkg.toml Lazy load chunks (#435) 6 years ago
LICENSE Add logo to readme. (#59) 7 years ago
Makefile Add a /ready endpoint to promtail 6 years ago
README.md Add Julien's blog post to the README. (#425) 6 years ago

README.md

Loki Logo

CircleCI Go Report Card Slack

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

Getting started

The getting started docs have instructions on how to install Loki via Docker images, Helm charts, Jsonnet, or from source.

Once you have promtail, Loki, and Grafana running, continue with our usage docs on how to query your logs.

Documentation

  • API documentation for alternative ways of getting logs into Loki.
  • Operations for important aspects of running Loki.
  • Promtail on how to configure the agent that tails your logs.
  • Logcli on how to query your logs without Grafana.
  • Troubleshooting for help around frequent error messages.
  • Usage for how to set up a Loki datasource in Grafana and query your logs.

Getting Help

If you have any questions or feedback regarding Loki:

Your feedback is always welcome.

Further Reading

Contributing

Refer to CONTRIBUTING.md

License

Apache License 2.0, see LICENSE.