Install loki with Homebrew, apk, apt, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• loki

Project history

Grafana Labs started Loki in 2018 and announced it at KubeCon Seattle. The official repository was created in April 2018 and describes the project as 'like Prometheus, but for logs.'

Loki was designed around labels, compressed unstructured logs, and integration with Grafana. The README explains that a Loki-based stack includes the Loki service, Grafana for querying and visualization, and a log collection agent; current docs identify Grafana Alloy as the forward-looking agent while Promtail is considered feature complete.

Grafana announced the general availability of Loki 1.0 in November 2019. By the 3.x series, Loki had grown into one of Grafana Labs' major OSS projects, with active documentation for single-binary, simple scalable, and microservices deployment modes.

Adoption history

Loki's adoption followed cloud-native observability patterns: Prometheus users already had label conventions, Grafana dashboards, and a need to correlate metrics and logs without paying the storage cost of full-text log indexing.

Grafana's official OSS pages and yearly open-source recap describe Loki as a major Grafana Labs project, and the repository shows broad adoption with tens of thousands of stars, thousands of forks, active releases, and an `ADOPTERS.md` process for organizations using Loki.

The supplied package facts show package-manager availability through Homebrew, Alpine, Debian, Ubuntu, Arch, Nix, and openSUSE-related packaging, with `logcli` also packaged separately in some ecosystems.

How it is used

Loki is usually launched with a YAML configuration file, commonly called `loki.yaml`, passed through `-config.file`. The official README's source build example runs `./cmd/loki/loki -config.file=./cmd/loki/loki-local-config.yaml`, and the docs show Docker examples using `/etc/loki/local-config.yaml`.

Operators send logs to Loki with agents such as Grafana Alloy, then query them from Grafana using LogQL. Loki's distinction is that labels are indexed, while log lines remain compressed payloads.

Why package nerds care

For package nerds, Loki is the observability-era package that made 'logs as Prometheus-shaped data' a concrete binary and config file. It is large enough to need Helm charts, Docker images, agents, and CLI companions, but still keeps a recognizable single-service local mode for packaging and testing.

Timeline

• 2018: Loki project starts at Grafana Labs and is announced at KubeCon Seattle.
• 2019: Grafana Labs announces Loki 1.0 general availability.
• 2022: Grafana Labs describes Loki as its second most popular OSS project behind Grafana.
• 2026: Loki 3.7.x releases are active in the official GitHub repository.

Related projects

• Loki is designed to pair with Grafana for visualization and with Prometheus-style labels for correlation with metrics.
• Promtail was the original log collection agent in many Loki deployments, while Grafana Alloy is now the recommended forward-looking collector in the README.

Sources

• https://api.github.com/repos/grafana/loki
• https://github.com/grafana/loki#readme
• https://grafana.com/blog/grafana-labs-open-source-projects-2022/
• https://grafana.com/docs/loki/latest/
• https://grafana.com/docs/loki/latest/configure/
• https://grafana.com/oss/loki/
• https://grafana.com/press/2019/11/20/grafana-labs-announces-ga-release-of-loki-like-prometheus-but-for-logs/
• source_facts.package-manager