logo

grafana/loki

Like Prometheus, but for logs.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Type:Server / PlatformCategory(s):Logging & TracingObservability & MonitoringDevOps & Observability
Added to GitGenius on July 24th, 2022
Created on April 16th, 2018
Open Issues & Pull Requests: 1,052 (+0)
GitHub issues: Enabled
Number of forks: 4,132
Total Stargazers: 29,002 (+0)
Total Subscribers: 384 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.4 days
Mean response time: 308.4 days
90th percentile: 1155.1 days
Tracked items: 2,418

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

14 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 19% of issues opened in the past year have never received a reply. 97% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "upgrade" is answered fastest, typically in about 5 days, while "keepalive" waits about 16 months. 55% of tracked open issues have had no activity in three months. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 546
New in 7 days: 7
Closed in 7 days: 175
Avg open age: 566 days
Stale 30+ days: 509
Stale 90+ days: 458

Recent activity

Opened in 7 days: 5
Closed in 7 days: 16
Comments in 7 days: 1
Events in 7 days: 6

Top labels

  • type/bug (636)
  • type/feature (377)
  • stale (332)
  • area/helm (329)
  • type/question (308)
  • type/docs (180)
  • component/promtail (161)
  • keepalive (161)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

Loki is a horizontally-scalable, multi-tenant log aggregation system built in Go and inspired by Prometheus. Rather than performing full-text indexing on log contents, Loki stores compressed, unstructured logs while indexing only metadata labels, making it significantly cheaper to operate and simpler to maintain than traditional log aggregation systems. The system is designed to work seamlessly with Prometheus by using the same label-based approach for both metrics and logs, allowing users to switch between the two using identical label sets. This label-centric architecture makes Loki particularly well-suited for Kubernetes environments, where Pod labels and metadata are automatically scraped and indexed.

The Loki stack consists of three components: Alloy, which is the agent responsible for gathering logs and sending them to Loki; Loki itself, which stores logs and processes queries; and Grafana, which provides the interface for querying and displaying logs. Alloy replaced Promtail as the primary log collection agent, with Promtail now considered feature-complete while future development focuses on Alloy's expanded capabilities. Loki has native support in Grafana starting from version 6.0, enabling integrated observability workflows.

The repository shows active development and community engagement.

The repository's scope extends across multiple operational domains. Documentation covers API usage for ingesting logs, label configuration, operational procedures, Docker driver integration for direct container log shipping, LogCLI for command-line querying, Loki Canary for monitoring log delivery, and troubleshooting guidance. A significant operational note indicates that as of March 16, 2026, the Grafana Loki Helm chart is being forked to a new repository at grafana-community/helm-charts, with the original repository maintaining the chart only for Grafana Enterprise Loki users.

The codebase is distributed under AGPL-3.0-only with Apache-2.0 exceptions documented in LICENSING.md. The project provides multiple support channels including a community forum, Slack workspace, GitHub issues, and a Google Groups mailing list, reflecting its position as an established cloud-native observability tool within the Grafana ecosystem.