cortexproject/cortex

A horizontally scalable, highly available, multi-tenant, long term Prometheus.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 58 seconds ago
Added to GitGenius on September 11th, 2026
Created on September 9th, 2016
Open Issues & Pull Requests: 348 (+0)
GitHub issues: Enabled
Number of forks: 876
Total Stargazers: 5,862 (+0)
Total Subscribers: 97 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.0 days
Mean response time: 51.6 days
90th percentile: 122.0 days
Tracked items: 290

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 75% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 73% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 9% of issues opened in the past year have been closed. Three people close 78% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 128
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 649 days
Stale 30+ days: 119
Stale 90+ days: 106

Recent activity

Opened in 7 days: 0
Closed in 7 days: 2
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • type/bug (72)
  • type/feature (60)
  • type/flaky-test (42)
  • help wanted (41)
  • stale (32)
  • component/ingester (31)
  • component/querier (30)
  • component/compactor (27)

Detailed Description

Cortex is a horizontally scalable, highly available, multi-tenant long-term storage solution for Prometheus and OpenTelemetry Metrics.

Cortex solves the problem of scaling Prometheus beyond a single machine while maintaining high availability and supporting long-term metric retention. It achieves this by distributing metric ingestion and querying across a cluster, replicating data between machines for fault tolerance, and isolating data from multiple independent Prometheus sources within a single deployment. The tool supports multiple cloud storage backends including S3, GCS, Swift, and Microsoft Azure for persistent metric storage.

Teams should adopt Cortex when they need to scale Prometheus horizontally across multiple machines, require multi-tenant isolation for independent metric sources, or want to retain metrics long-term in cloud object storage. It suits organizations running Prometheus at scale in Kubernetes environments where a single Prometheus instance cannot handle the throughput or storage requirements. The project is particularly valuable for those seeking to consolidate multiple Prometheus instances into a unified, highly available cluster.

The project receives issue reports primarily from outside users rather than the core team, reflecting a substantial base of adopters running it in production. Responses to issues and pull requests typically arrive within one to two weeks. Work in the issue tracker centers on bug fixes, feature requests, and flaky test resolution, indicating active maintenance focused on stability and incremental improvements.