loki: A horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus.
What problem it solves
Organizations need to aggregate, store, and query logs without operating a complex full-text indexing system. Loki addresses this with compressed, unstructured logs and metadata-based indexing using labels that can also be used to switch between metrics and logs.
Key features
Label-based log indexing — Loki stores compressed log content and indexes labels associated with each log stream rather than indexing the full text of logs.
Source: README
Scalable multi-tenant aggregation — The system is designed for horizontal scaling, high availability, and multi-tenant log aggregation.
Source: README
Simple single-binary operation — Loki can run in a single-host, no-dependencies mode, making it straightforward to build and run locally.
Source: README, cmd
Integrated logging stack — The documented stack combines Alloy for log collection, Loki for storage and query processing, and Grafana for querying and displaying logs.
Source: README
Kubernetes log support — Loki is positioned as a suitable system for Kubernetes Pod logs, with Pod metadata automatically scraped and indexed.
Source: README
Quick start
Copied verbatim from the project's README.
# Build binary
$ make loki
# Run executable
$ ./cmd/loki/loki -config.file=./cmd/loki/loki-local-config.yamlWho it may suit
Inference: may suit teams operating cloud-native environments that need multi-tenant log aggregation, especially those collecting Kubernetes Pod logs and querying them through Grafana.
Topics to discuss
How should operators balance label cardinality against storage and query requirements?
What workflows are most effective when moving from Promtail to Alloy for log collection?
Which operational practices are essential for maintaining reliable ingestion and query processing?
Written by ReadmeX AI from the project's README, source and public GitHub data; it may contain mistakes.
Read the original README https://github.com/grafana/loki#readme
ReadmeX opened this community for a trending project; it is not run by the project. Maintainers can claim it from the community page.
Comments
…