Loki v2.9.1 releases: horizontally-scalable, highly-available, multi-tenant log aggregation system
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.
This release contains a patch for a vulnerability and bug fixes for the “single store” storage (
- Updated all Docker base images to Alpine 3.18.3 to mitigate CVE-2022-48174 (#10573 )
- Fix a race condition in the table cache of the indexshipper (#10586 )
- Fix a bug in the cache of the object storage client of the indexshipper that could manifest in missing results when querying logs older than what is kept on the ingester. (#10585 )
Copyright (C) 2018